Portable multifunction device, method, and graphical user interface for viewing and managing electronic calendars

ABSTRACT

In accordance with some embodiments, a computer-implemented method is performed at a portable multifunction device with a touch screen display. The computer-implemented method includes displaying a multiweek calendar on the touch screen display, detecting a contact on an individual day in the multiweek calendar, and in response to detecting the contact on the individual day, displaying at least a portion of a list of events on the contacted individual day while continuing to display the multiweek calendar, wherein the list of events on the contacted individual day includes an invitation to an event.

RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.15/730,450, “Portable Multifunction Device, Method, and Graphical UserInterface for Viewing and Managing Electronic Calendars,” filed Oct. 11,2017 which is a continuation of U.S. application Ser. No. 15/078,767,“Portable Multifunction Device, Method, and Graphical User Interface forViewing and Managing Electronic Calendars,” filed Mar. 23, 2016, whichis a divisional of U.S. application Ser. No. 13/666,944, filed Nov. 1,2012, issued as U.S. Pat. No. 9,330,381 on May 3, 2016, which is adivisional of U.S. application Ser. No. 12/242,856, filed Sep. 30, 2008,issued as U.S. Pat. No. 8,327,272, on Dec. 4, 2012, and which claimspriority to U.S. Provisional Patent Application Nos. 61/033,780,“Portable Multifunction Device, Method, and Graphical User Interface forViewing and Managing Electronic Calendars,” filed Mar. 4, 2008, and61/019,295, “Portable Multifunction Device, Method, and Graphical UserInterface for Displaying and Selecting Application Options,” filed Jan.6, 2008, all of which are incorporated herein by reference in theirentirety.

This application is related to the following applications: (1) U.S.patent application Ser. No. 10/188,182, “Touch Pad For Handheld Device,”filed on Jul. 1, 2002; (2) U.S. patent application Ser. No. 10/722,948,“Touch Pad For Handheld Device,” filed on Nov. 25, 2003; (3) U.S. patentapplication Ser. No. 10/643,256, “Movable Touch Pad With AddedFunctionality,” filed on Aug. 18, 2003; (4) U.S. patent application Ser.No. 10/654,108, “Ambidextrous Mouse,” filed on Sep. 2, 2003; (5) U.S.patent application Ser. No. 10/840,862, “Multipoint Touchscreen,” filedon May 6, 2004; (6) U.S. patent application Ser. No. 10/903,964,“Gestures For Touch Sensitive Input Devices,” filed on Jul. 30, 2004;(7) U.S. patent application Ser. No. 11/038,590, “Mode-Based GraphicalUser Interfaces For Touch Sensitive Input Devices” filed on Jan. 18,2005; (8) U.S. patent application Ser. No. 11/057,050, “DisplayActuator,” filed on Feb. 11, 2005; (10) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006;(11) U.S. patent application Ser. No. 11/850,635, “PortableMultifunction Device,” filed Sep. 5, 2007; (12) U.S. patent applicationSer. No. 11/969,800, “Modal Change Based on Orientation of a PortableMultifunction Device,” filed Jan. 4, 2008; (13) U.S. patent applicationSer. No. 11/969,786, “System and Method for Viewing and ManagingCalendar Entries,” filed Jan. 4, 2008; and (14) U.S. Provisional PatentApplication No. 61/019,293, “Portable Electronic Device withConversation Management for Incoming Instant Messages,” filed Jan. 6,2008. All of these applications are incorporated by reference herein intheir entirety.

TECHNICAL FIELD

The disclosed embodiments relate generally to portable electronicdevices, and more particularly, to portable devices for viewing andmanaging electronic calendars.

BACKGROUND

As portable electronic devices become more compact, and the number offunctions performed by a given device increases, it has become asignificant challenge to design a user interface that allows users toeasily interact with a multifunction device. This challenge isparticularly significant for handheld portable devices, which have muchsmaller screens than desktop or laptop computers. This situation isunfortunate because the user interface is the gateway through whichusers receive not only content but also responses to user actions orbehaviors, including user attempts to access a device's features, tools,and functions. Some portable communication devices (e.g., mobiletelephones, sometimes called mobile phones, cell phones, cellulartelephones, and the like) have resorted to adding more pushbuttons,increasing the density of push buttons, overloading the functions ofpushbuttons, or using complex menu systems to allow a user to access,store and manipulate data. These conventional user interfaces oftenresult in complicated key sequences and menu hierarchies that must bememorized by the user.

Many conventional user interfaces, such as those that include physicalpushbuttons, are also inflexible. This is unfortunate because it mayprevent a user interface from being configured and/or adapted by eitheran application running on the portable device or by users. When coupledwith the time consuming requirement to memorize multiple key sequencesand menu hierarchies, and the difficulty in activating a desiredpushbutton, such inflexibility is frustrating to most users.

Portable electronic devices often include a calendar application to keeptrack of meetings or appointments. Generally, the calendars on thesedevices may be viewed according to a monthly format, which displays arespective month, a daily format, which displays a respective day, or aweekly format, which displays, a respective week. In some of thesecalendars, a listing of agenda, or calendar entry items, may be viewedin list format. These formats are typically viewed separately, andswitching between them is often cumbersome and inconvenient.

Some portable devices are also able to receive and respond to calendarinvitations and/or display simultaneously entries from multiplecalendars (e.g., a work calendar and a personal calendar). But the userinterfaces for these functions are cryptic and non-intuitive for manyusers.

Accordingly, there is a need for portable multifunction devices withmore transparent and intuitive user interfaces for displaying andmanaging calendars and calendar entries on a touch screen display thatare easy to use, configure, and/or adapt.

SUMMARY

The above deficiencies and other problems associated with userinterfaces for portable devices are reduced or eliminated by thedisclosed portable multifunction device. In some embodiments, the devicehas a touch-sensitive display (also known as a “touch screen” or “touchscreen display”) with a graphical user interface (GUI), one or moreprocessors, memory and one or more modules, programs or sets ofexecutable instructions stored in the memory for performing multiplefunctions. In some embodiments, the user interacts with the GUIprimarily through finger contacts and gestures on the touch-sensitivedisplay. In some embodiments, in addition to providing a calendar, thefunctions may include telephoning, video conferencing, e-mailing,instant messaging, blogging, digital photographing, digital videoing,web browsing, digital music playing, and/or digital video playing.Instructions for performing these functions may be included in acomputer program product configured for execution by one or moreprocessors.

In accordance with some embodiments, a computer-implemented methodincludes executing a calendar application on a portable electronicdevice having a touch screen display. The executing includes: when thedevice is held in a portrait orientation, displaying a calendar in afirst view and showing events for a first time period in the first view.The executing also includes: detecting a change in orientation of thedevice to a landscape orientation, and in response, displaying thecalendar in a second view and showing events for a second time periodthat is longer than and includes the first time period.

In accordance with some embodiments, a portable electronic deviceincludes: a touch screen display; one or more processors; memory; andone or more programs. The one or more programs are stored in the memoryand configured to be executed by the one or more processors. The one ormore programs include: instructions for, when the device is held in aportrait orientation, displaying a calendar in a first view, showingevents for a first time period in the first view; and instructions fordetecting a change in orientation of the device to a landscapeorientation, and in response, displaying the calendar in a second view,showing events for a second time period that is longer than and includesthe first time period.

In accordance with some embodiments, a computer readable storage mediumhas stored therein instructions, which when executed by a portableelectronic device with a touch screen display, cause the device to: whenthe device is held in a portrait orientation, display a calendar in afirst view, showing events for a first time period in the first view;and detect a change in orientation of the device to a landscapeorientation, and in response, display the calendar in a second view,showing events for a second time period that is longer than and includesthe first time period.

In accordance with some embodiments, a graphical user interface on aportable electronic device with a touch screen display includes: acalendar with a first view that shows events for a first time period anda second view that shows events for a second time period. When thedevice is held in a portrait orientation, the calendar is displayed inthe first view that shows events for the first time period. In responseto detecting a change in orientation of the device to a landscapeorientation, the calendar is displayed in a second view that showsevents for the second time period. The second time period is longer thanand includes the first time period.

In accordance with some embodiments, a portable multifunction devicewith a touch screen display includes: means for, when the device is heldin a portrait orientation, displaying a calendar in a week view, showingevents for a single week in the week view; and means for detecting achange in orientation of the device to a landscape orientation, and inresponse, displaying the calendar in a multiweek view, showing eventsfor a multiplicity of weeks, the multiplicity of weeks including thesingle week.

In accordance with some embodiments, a computer-implemented method isperformed at a portable multifunction device with a touch screendisplay. The touch screen display includes a long axis, a short axis, aportrait view and a landscape view. The computer-implemented methodincludes executing a calendar application. The portable multifunctiondevice is detected in a first orientation that comprises a substantiallyvertical orientation of the long axis. In response to detecting theportable multifunction device in the first orientation that comprisesthe substantially vertical orientation of the long axis, a calendar isdisplayed for a first time period in the portrait view. The portablemultifunction device is detected in a second orientation that comprisesa substantially vertical orientation of the short axis. In response todetecting the portable multifunction device in the second orientationthat comprises the substantially vertical orientation of the short axis,a calendar is displayed for a second time period in the landscape view.The second time period is longer than and includes the first timeperiod.

In accordance with some embodiments, a portable multifunction deviceincludes a touch screen display, one or more processors, memory, and oneor more programs. The touch screen display includes a long axis, a shortaxis, a portrait view and a landscape view. The one or more programs arestored in the memory and configured to be executed by the one or moreprocessors. The one or more programs include: instructions for executinga calendar application; instructions for detecting the portablemultifunction device in a first orientation that comprises asubstantially vertical orientation of the long axis; instructions fordisplaying a calendar for a first time period in the portrait view inresponse to detecting the portable multifunction device in the firstorientation that comprises the substantially vertical orientation of thelong axis; instructions for detecting the portable multifunction devicein a second orientation that comprises a substantially verticalorientation of the short axis; and instructions for displaying acalendar for a second time period in the landscape view in response todetecting the portable multifunction device in the second orientationthat comprises the substantially vertical orientation of the short axis.The second time period is longer than and includes the first timeperiod.

In accordance with some embodiments, a computer readable storage mediumhas stored therein instructions, which when executed by a portablemultifunction device with a touch screen display (wherein the touchscreen display includes a long axis, a short axis, a portrait view and alandscape view), cause the device to: execute a calendar application;detect the portable multifunction device in a first orientation thatcomprises a substantially vertical orientation of the long axis; displaya calendar for a first time period in the portrait view in response todetecting the portable multifunction device in the first portablemultifunction device in a second orientation that comprises asubstantially vertical orientation of the short axis; and display acalendar for a second time period in the landscape view in response todetecting the portable multifunction device in the second orientationthat comprises the substantially vertical orientation of the short axis.The second time period is longer than and includes the first timeperiod.

In accordance with some embodiments, a graphical user interface on aportable multifunction device with a touch screen display includes: acalendar application; a calendar for a first time period; and a calendarfor a second time period. The touch screen display includes a long axis,a short axis, a portrait view and a landscape view. In response todetecting the portable multifunction device in a first orientation thatcomprises a substantially vertical orientation of the long axis, thecalendar for the first time period is displayed in the portrait view. Inresponse to detecting the portable multifunction device in a secondorientation that comprises a substantially vertical orientation of theshort axis, the calendar for a second time period is displayed in thelandscape view. The second time period is longer than and includes thefirst time period

In accordance with some embodiments, a portable multifunction devicewith a touch screen display (wherein the touch screen display includes along axis, a short axis, a portrait view and a landscape view) includes:means for executing a calendar application; means for detecting theportable multifunction device in a first orientation that comprises asubstantially vertical orientation of the long axis; means fordisplaying a calendar for a first time period in the portrait view inresponse to detecting the portable multifunction device in the firstorientation that comprises the substantially vertical orientation of thelong axis; means for detecting the portable multifunction device in asecond orientation that comprises a substantially vertical orientationof the short axis; and means for displaying a calendar for a second timeperiod in the landscape view in response to detecting the portablemultifunction device in the second orientation that comprises thesubstantially vertical orientation of the short axis. The second timeperiod is longer than and includes the first time period.

In accordance with some embodiments, a computer-implemented method isperformed at a portable multifunction device with a touch screendisplay. The computer-detecting a contact on an individual day in themultiweek calendar; and, in response to detecting the contact on theindividual day, displaying at least a portion of a list of events on thecontacted individual day while continuing to display the multiweekcalendar. The list of events on the contacted individual day includes aninvitation to an event.

In accordance with some embodiments, a portable multifunction deviceincludes: a touch screen display; one or more processors; memory; andone or more programs. The one or more programs are stored in the memoryand configured to be executed by the one or more processors. The one ormore programs include: instructions for displaying a multiweek calendaron the touch screen display; instructions for detecting a contact on anindividual day in the multiweek calendar; and instructions fordisplaying at least a portion of a list of events on the contactedindividual day while continuing to display the multiweek calendar inresponse to detecting the contact on the individual day. The list ofevents on the contacted individual day includes an invitation to anevent.

In accordance with some embodiments, a computer readable storage mediumhas stored therein instructions, which when executed by a portablemultifunction device with a touch screen display, cause the portablemultifunction device to: display a multiweek calendar on the touchscreen display; detect a contact on an individual day in the multiweekcalendar; and, in response to detecting the contact on the individualday, display at least a portion of a list of events on the contactedindividual day while continuing to display the multiweek calendar. Thelist of events on the contacted individual day includes an invitation toan event.

In accordance with some embodiments, a graphical user interface on aportable multifunction device with a touch screen display includes: acalendar application; a multiweek calendar including a plurality ofdays; and a list of events associated with at least one of the pluralityof days, the list of events including at least one invitation to anevent. In response to detecting a contact on an individual day in themultiweek calendar, at least a portion of the list of events on thecontacted individual day are displayed while continuing to display themultiweek calendar.

In accordance with some embodiments, a portable multifunction devicewith a touch screen display includes: means for displaying a multiweekcalendar on the touch screen display; means for detecting a contact onan individual day of the multiweek calendar; and means for displaying atleast a portion of a list of events on the contacted individual daywhile continuing to display the multiweek calendar in response todetecting the contact on the individual day. The list of events on thecontacted individual day includes an invitation to an event.

In accordance with some embodiments, a computer-implemented method isperformed at a portable multifunction device with a touch screendisplay. The computer-implemented method includes: displaying a flatversion of a calendar application interface, and, in response todetecting a user gesture on a view options icon while the flat versionof the calendar application interface is displayed, displaying a curledversion of the calendar application interface. The curled version of thecalendar application interface includes an image of a curled page thatobscures a first portion of the flat version of the calendar applicationinterface, and a roll-up region in a display region formerly occupied bya second portion of the flat version of the calendar applicationinterface. The roll-up region includes a plurality of calendar optionicons, each respective calendar option icon in the plurality of calendaroption icons responsive to a user selection gesture on the respectivecalendar option icon. The computer-implemented method also includes:detecting a user selection gesture on one or more of the plurality ofcalendar option icons, and redisplaying the flat version of the calendarapplication interface with information corresponding to the one or morecalendar option icons upon which user selection gestures were detected.

In accordance with some embodiments, a portable computing deviceincludes: a touch screen display; one or more processors; memory; andone or more programs. The one or more programs are stored in the memoryand configured to be executed by the one or more processors. The one ormore programs include: instructions for displaying a flat version of acalendar application interface; instructions for displaying a curledversion of the calendar application interface in response to detecting auser gesture on a view options icon while the flat version of thecalendar application interface is displayed. The curled version of thecalendar application interface includes: an image of a curled page thatobscures a first portion of the flat version of the calendar applicationinterface, and a roll-up region in a display region formerly occupied bya second portion of the flat version of the calendar applicationinterface. The roll-up region includes a plurality of calendar optionicons, each respective calendar option icon in the plurality of calendarThe one or more programs also include: instructions for detecting a userselection gesture on one or more of the plurality of calendar optionicons; and instructions for redisplaying the flat version of thecalendar application interface with information corresponding to the oneor more calendar option icons upon which user selection gestures weredetected.

In accordance with some embodiments, a computer readable storage mediumhas stored therein instructions, which when executed by a portablemultifunction device with a touch screen display, cause the portablemultifunction device to: display a flat version of a calendarapplication interface; and display a curled version of the calendarapplication interface in response to detecting a user gesture on a viewoptions icon while the flat version of the calendar applicationinterface is displayed. The curled version of the calendar applicationinterface includes: an image of a curled page that obscures a firstportion of the flat version of the calendar application interface, and aroll-up region in a display region formerly occupied by a second portionof the flat version of the calendar application interface. The roll-upregion includes a plurality of calendar option icons, each respectivecalendar option icon in the plurality of calendar option iconsresponsive to a user selection gesture on the respective calendar optionicon. The instructions also cause the portable multifunction device to:detect a user selection gesture on one or more of the plurality ofcalendar option icons; and redisplay the flat version of the calendarapplication interface with information corresponding to the one or morecalendar option icons upon which user selection gestures were detected.

In accordance with some embodiments, a graphical user interface on aportable multifunction device with a touch screen display includes aflat version of a calendar application interface; a calendar optionsicon; and a curled version of the calendar application interface. Thecurled version of the calendar application interface includes an imageof a curled page that obscures a first portion of the flat version ofthe calendar application interface, and a roll-up region in a displayregion formerly occupied by a second portion of the flat version of thecalendar application interface. The roll-up region includes a pluralityof calendar option icons, each respective calendar option icon in theplurality of calendar option icons responsive to a user selectiongesture on the respective calendar option icon. In response to detectinga user gesture on the calendar options icon while the flat version ofthe calendar application interface is displayed, the curled version ofthe calendar application interface is displayed. In response todetecting user selection gestures on one or more of the plurality ofcalendar option icons, the flat version of the calendar applicationinterface is redisplayed with information corresponding to the one ormore of the plurality of calendar option icons upon which user selectiongestures were detected.

In accordance with some embodiments, a portable multifunction devicewith a touch screen display includes: means for displaying a flatversion of a calendar application interface; and means for displaying acurled version of the calendar application interface in response todetecting a user gesture on a view options icon while the flat versionof the calendar application interface is displayed. The curled versionof the calendar application interface includes: an image of a curledpage that obscures a first portion of the flat version of the calendarapplication interface, and a roll-up region in a display region formerlyoccupied by a second portion of the flat version of the calendarapplication interface. The roll-up region includes a plurality ofcalendar option icons, each respective calendar option icon in theplurality of calendar option icons responsive to a user selectiongesture on the respective calendar option icon. The device alsoincludes: means for detecting a user selection gesture on one or more ofthe plurality of calendar option icons; and means for redisplaying theflat version of the calendar application interface with informationcorresponding to the one or more calendar option icons upon which userselection gestures were detected.

In accordance with some embodiments, a computer-implemented method isperformed at a portable multifunction device with a touch screendisplay. The computer-implemented method includes: receiving a calendarinvitation, from a party to a user of the device, while the device islocked; displaying at least a portion of the calendar invitation on thetouch screen display while the device remains locked; and, in responseto detecting a user request to view the calendar invitation, immediatelydisplaying the calendar invitation in a calendar application.

In accordance with some embodiments, a portable computing deviceincludes: a touch screen display; one or more processors; memory; andone or more programs. The one or more programs are stored in the memoryand configured to be executed by the one or more processors. The one ormore programs include: instructions for receiving a calendar invitation,from a party to a user of the device, while the device is locked;instructions for displaying at least a portion of the calendarinvitation on the touch screen display while the device remains locked;and instructions for immediately displaying the calendar invitation in acalendar application in response to detecting a user request to view thecalendar invitation.

In accordance with some embodiments, a computer readable storage mediumhas stored therein instructions, which when executed by a portablemultifunction device with a touch screen display, cause the portablemultifunction device to: receive a calendar invitation, from a party toa user of the device, while the device is locked; display at least aportion of the calendar invitation on the touch screen display while thedevice remains locked; and, in response to detecting a user request toview the calendar invitation, immediately display the calendarinvitation in a calendar application.

In accordance with some embodiments, a graphical user interface on aportable multifunction device with a touch screen display includes: acalendar application; and at least a portion of a calendar invitation.In response to receiving the calendar invitation from a party to a userof the device while the device is locked, at least the portion of thecalendar invitation is displayed on the touch screen display while thedevice remains locked. In response to detecting a user request to viewthe calendar invitation, the calendar invitation is immediatelydisplayed in the calendar application.

In accordance with some embodiments, a portable multifunction devicewith a touch screen display includes: means for receiving a calendarinvitation, from a party to a user of the device, while the device islocked; means for displaying at least a portion of the calendarinvitation on the touch screen display while the device remains locked;and means for immediately displaying the calendar invitation in acalendar application in response to detecting a user request to view thecalendar invitation.

Thus, the invention provides an intuitive, easy-to-use interface fordisplaying and managing calendars and calendar entries on a portablemultifunction device with a touch screen display.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the aforementioned embodiments of theinvention as well as additional embodiments thereof, reference should bemade to the like reference numerals refer to corresponding partsthroughout the figures.

FIGS. 1 A and 1B are block diagrams illustrating portable multifunctiondevices with touch-sensitive displays in accordance with someembodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 illustrates an exemplary user interface for unlocking a portableelectronic device in accordance with some embodiments.

FIGS. 4A and 4B illustrate exemplary user interfaces for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIGS. 5A-5M illustrate exemplary user interfaces for displaying andmanaging calendar entries in accordance with some embodiments.

FIGS. 6A-6B are flow diagrams of processes for displaying and managingcalendar entries in accordance with some embodiments.

FIGS. 7A-7S illustrate exemplary user interfaces for accessing acalendar application on a portable multifunction device in accordancewith some embodiments.

FIG. 8A-8F are flow diagrams illustrating methods of operating acalendar application in accordance with some embodiments.

FIG. 9 is a schematic diagram of a communications system that providesinfrastructure support for a portable multifunction device in accordancewith some embodiments.

DESCRIPTION OF EMBODIMENTS

Reference will now be made in detail to embodiments, examples of whichare illustrated in the accompanying drawings. In the following detaileddescription, numerous specific details are set forth in order to providea thorough understanding of the present invention. However, it will beapparent to one of ordinary skill in the art that the present inventionmay be practiced without these specific details. In other instances,well-known methods, procedures, components, circuits, and networks havenot been described in detail so as not to unnecessarily obscure aspectsof embodiments.

It will also be understood that, although the terms first, second, etc.may be used herein to describe various elements, these elements shouldnot be limited by these terms. These terms are only used to distinguishone element from another. For example, a first gesture could be termed asecond gesture, and, similarly, a second gesture could be termed a firstgesture, without departing from the scope of the present invention.

The terminology used in the description of the invention herein is forthe purpose of describing particular embodiments only and is notintended to be limiting of the invention. As used in the description ofthe invention and the appended claims, the singular forms “a”, “an” and“the” are intended to include the plural forms as well, unless thecontext clearly indicates otherwise. It will also be understood that theterm “and/or” as used herein refers to and encompasses any and allpossible combinations of one or more of the associated listed items. Itwill be further understood that the terms “comprises” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

Embodiments of a portable multifunction device, user interfaces for suchdevices, and associated processes for using such devices are described.In some embodiments, the device is a portable communications device suchas a mobile telephone that also contains other functions, such as PDAand/or music player functions.

The user interface may include a physical click wheel in addition to atouch screen or a virtual click wheel displayed on the touch screen. Aclick wheel is a user-interface device that may provide navigationcommands based on an angular displacement of the wheel or a point ofcontact with the wheel by a user of the device. A click wheel may alsobe used to provide a user command corresponding to selection of one ormore items, for example, when the user of the device presses down on atleast a portion of the wheel or the center of the wheel. Alternatively,breaking contact with a click wheel image on a touch screen surface mayindicate a user command corresponding to selection. For simplicity, inthe discussion that follows, a portable multifunction device thatincludes a touch screen is used as an exemplary embodiment. It should beunderstood, however, that some of the user interfaces and associatedprocesses may be applied to other devices, such as personal computersand laptop computers, that may include one or more other physicaluser-interface devices, such as a physical click wheel, a physicalkeyboard, a mouse and/or a joystick.

In addition to a calendar application, the device may support a varietyof other applications, such as one or more of the following: a telephoneapplication, a video conferencing application, an e-mail application, aninstant messaging application, a blogging application, a digital cameraapplication, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that may be executed on the device may use atleast one common physical user-interface device, such as the touchscreen. One or more functions of the touch screen as well ascorresponding information displayed on the device may be adjusted and/orvaried from one application to the next and/or within a respectiveapplication. In this way, a common physical architecture (such as thetouch screen) of the device may support the variety of applications withuser interfaces that are intuitive and transparent.

The user interfaces may include one or more soft keyboard embodiments.The soft keyboard embodiments may include standard (QWERTY) and/ornon-standard configurations of symbols on the displayed icons of thekeyboard, such as those described in U.S. patent application Ser. No.11/459,606, “Keyboards For Portable Electronic Devices,” filed Jul. 24,2006, and Ser. No. 11/459,615, “Touch Screen Keyboards For PortableElectronic Devices,” filed Jul. 24, 2006, the contents of which arehereby incorporated by reference in their entirety. The keyboardembodiments may include a reduced number of icons (or soft keys)relative to the number of keys in existing physical keyboards, such asthat for a typewriter. This may make it easier for users to select oneor more icons in the keyboard, and thus, one or more correspondingsymbols. The keyboard embodiments may be adaptive. For example,displayed icons may be modified in accordance with user actions, such asselecting one or more icons and/or one or more corresponding symbols.One or more applications on the portable device may utilize commonand/or different keyboard embodiments. Thus, the keyboard embodimentused may be tailored to at least some of the applications. In someembodiments, one or more keyboard embodiments may be tailored to arespective user. For example, one or more keyboard embodiments may betailored to a respective user. Some of the keyboard embodiments may beadjusted to reduce a probability of a user error when selecting one ormore icons, and thus one or more symbols, when using the soft keyboardembodiments.

Attention is now directed towards embodiments of the device. FIGS. 1Aand 1B are block diagrams illustrating portable multifunction devices100 with touch-sensitive displays 112 in accordance with someembodiments. The touch-sensitive display 112 is sometimes called a“touch screen” for convenience, and may also be known as or called atouch-sensitive display system. The device 100 may include a memory 102(which may include one or more computer readable storage mediums), amemory controller 122, one or more processing units (CPU's) 120, aperipherals interface 118, RF circuitry 108, audio circuitry 110, aspeaker 111, a microphone 113, an input/output (I/O) subsystem 106,other input or control devices 116, and an external port 124. The device100 may include one or more optical sensors 164. These components maycommunicate over one or more communication buses or signal lines 103.

It should be appreciated that the device 100 is only one example of aportable multifunction device 100, and that the device 100 may have moreor fewer components than shown, may combine two or more components, or amay have a different configuration or arrangement of the components. Thevarious components shown in FIGS. 1A and 1B may be implemented inhardware, software or a combination of both hardware and software,including one or more signal processing and/or application specificintegrated circuits.

Memory 102 may include high-speed random access memory and may alsoinclude non-volatile memory, such as one or more magnetic disk storagedevices, flash memory devices, or other non-volatile solid-state memorydevices. Access to memory 102 by other components of the device 100,such as the CPU 120 and the peripherals interface 118, may be controlledby the memory controller 122.

The peripherals interface 118 couples the input and output peripheralsof the device to the CPU 120 and memory 102. The one or more processors120 run or execute various software programs and/or sets of instructionsstored in memory 102 to perform various functions for the device 100 andto process data.

In some embodiments, the peripherals interface 118, the CPU 120, and thememory controller 122 may be implemented on a single chip, such as achip 104. In some other embodiments, they may be implemented on separatechips.

The RF (radio frequency) circuitry 108 receives and sends RF signals,also called electromagnetic signals. The RF circuitry 108 convertselectrical signals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. The RF circuitry 108 may include well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. The RFcircuitry 108 may communicate with networks, such as the Internet, alsoreferred to as the World Wide Web (WWW), an intranet and/or a wirelessnetwork, such as a cellular telephone network, a wireless local areanetwork (LAN) and/or a metropolitan area network (MAN), and otherdevices by wireless communication. The wireless communication may useany of a plurality of communications standards, protocols andtechnologies, including but not limited to Global System for MobileCommunications (GSM), Enhanced Data GSM Environment (EDGE), high-speeddownlink packet access (HSDPA), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a,IEEE 802.11b, IEEE 802.11g and/or IEEE 802.11n), voice over InternetProtocol (VoIP), Wi-MAX, a protocol for email (e.g., Internet messageaccess protocol (IMAP) and/or post office protocol (POP)), instantmessaging (e.g., extensible messaging and presence protocol (XMPP),Session Initiation Protocol for Instant Messaging and PresenceLeveraging Extensions (SIMPLE), and/or Instant Messaging and PresenceService (IMPS)), and/or Short Message Service (SMS)), or any othersuitable communication protocol, including communication protocols notyet developed as of the filing date of this document.

The audio circuitry 110, the speaker 111, and the microphone 113 providean audio interface between a user and the device 100. The audiocircuitry 110 receives audio data from the peripherals interface 118,converts the audio data to an electrical signal, and transmits theelectrical signal to the speaker 111. The speaker 111 converts theelectrical signal to human-audible sound waves. The audio circuitry 110also receives electrical converts the electrical signal to audio dataand transmits the audio data to the peripherals interface 118 forprocessing. Audio data may be retrieved from and/or transmitted tomemory 102 and/or the RF circuitry 108 by the peripherals interface 118.In some embodiments, the audio circuitry 110 also includes a headsetjack (e.g. 212, FIG. 2). The headset jack provides an interface betweenthe audio circuitry 110 and removable audio input/output peripherals,such as output-only headphones or a headset with both output (e.g., aheadphone for one or both ears) and input (e.g., a microphone).

The I/O subsystem 106 couples input/output peripherals on the device100, such as the touch screen 112 and other input/control devices 116,to the peripherals interface 118. The I/O subsystem 106 may include adisplay controller 156 and one or more input controllers 160 for otherinput or control devices. The one or more input controllers 160receive/send electrical signals from/to other input or control devices116. The other input/control devices 116 may include physical buttons(e.g., push buttons, rocker buttons, etc.), dials, slider switches,joysticks, click wheels, and so forth. In some alternate embodiments,input controller(s) 160 may be coupled to any (or none) of thefollowing: a keyboard, infrared port, USB port, and a pointer devicesuch as a mouse. The one or more buttons (e.g., 208, FIG. 2) may includean up/down button for volume control of the speaker 111 and/or themicrophone 113. The one or more buttons may include a push button (e.g.,206, FIG. 2). A quick press of the push button may disengage a lock ofthe touch screen 112 or begin a process that uses gestures on the touchscreen to unlock the device, as described in U.S. patent applicationSer. No. 11/322,549, “Unlocking a Device by Performing Gestures on anUnlock Image,” filed Dec. 23, 2005, which is hereby incorporated byreference in its entirety. A longer press of the push button (e.g., 206)may turn power to the device 100 on or off The user may be able tocustomize a functionality of one or more of the buttons. The touchscreen 112 is used to implement virtual or soft buttons and one or moresoft keyboards.

The touch-sensitive touch screen 112 provides an input interface and anoutput interface between the device and a user. The display controller156 receives and/or sends electrical signals from/to the touch screen112. The touch screen 112 displays visual output to the user. The visualoutput may include graphics, text, icons, video, and any combinationthereof (collectively termed “graphics”). In some embodiments, some orall of described below.

A touch screen 112 has a touch-sensitive surface, sensor or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. The touch screen 112 and the display controller 156 (along withany associated modules and/or sets of instructions in memory 102) detectcontact (and any movement or breaking of the contact) on the touchscreen 112 and converts the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages orimages) that are displayed on the touch screen. In an exemplaryembodiment, a point of contact between a touch screen 112 and the usercorresponds to a finger of the user.

The touch screen 112 may use LCD (liquid crystal display) technology, orLPD (light emitting polymer display) technology, although other displaytechnologies may be used in other embodiments. The touch screen 112 andthe display controller 156 may detect contact and any movement orbreaking thereof using any of a plurality of touch sensing technologiesnow known or later developed, including but not limited to capacitive,resistive, infrared, and surface acoustic wave technologies, as well asother proximity sensor arrays or other elements for determining one ormore points of contact with a touch screen 112.

A touch-sensitive display in some embodiments of the touch screen 112may be analogous to the multi-touch sensitive tablets described in thefollowing U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat. No.6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932(Westerman), and/or U.S. Patent Publication 2002/0015024A1, each ofwhich is hereby incorporated by reference in its entirety. However, atouch screen 112 displays visual output from the portable device 100,whereas touch sensitive tablets do not provide visual output.

A touch-sensitive display in some embodiments of the touch screen 112may be as described in the following applications: (1) U.S. patentapplication Ser. No. 11/381,313, “Multipoint Touch Surface Controller,”filed May 2, 2006; (2) U.S. patent application Ser. No. 10/840,862,“Multipoint Touchscreen,” filed May 6, 2004; (3) U.S. patent applicationSer. No. 10/903,964, “Gestures For Touch Sensitive Input Devices,” filedJul. 30, 2004; (4) U.S. patent application Ser. No. 11/048,264,“Gestures For Touch Sensitive Input Devices,” filed Jan. 31, 2005; (5)U.S. patent application Ser. No. 11/038,590, “Mode-Based Graphicalapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

The touch screen 112 may have a resolution in excess of 100 dpi. In anexemplary embodiment, the touch screen has a resolution of approximately160 dpi. The user may make contact with the touch screen 112 using anysuitable object or appendage, such as a stylus, a finger, and so forth.In some embodiments, the user interface is designed to work primarilywith finger-based contacts and gestures, which are much less precisethan stylus-based input due to the larger area of contact of a finger onthe touch screen. In some embodiments, the device translates the roughfinger-based input into a precise pointer/cursor position or command forperforming the actions desired by the user.

In some embodiments, in addition to the touch screen, the device 100 mayinclude a touchpad (not shown) for activating or deactivating particularfunctions. In some embodiments, the touchpad is a touch-sensitive areaof the device that, unlike the touch screen, does not display visualoutput. The touchpad may be a touch-sensitive surface that is separatefrom the touch screen 112 or an extension of the touch-sensitive surfaceformed by the touch screen.

In some embodiments, the device 100 may include a physical or virtualclick wheel as an input control device 116. A user may navigate amongand interact with one or more graphical objects (henceforth referred toas icons) displayed in the touch screen 112 by rotating the click wheelor by moving a point of contact with the click wheel (e.g., where theamount of movement of the point of contact is measured by its angulardisplacement with respect to a center point of the click wheel). Theclick wheel may also be used to select one or more of the displayedicons. For example, the user may press down on at least a portion of theclick wheel or an associated button. User commands and navigationcommands provided by the user via the click wheel may be processed by aninput controller virtual click wheel, the click wheel and click wheelcontroller may be part of the touch screen 112 and the displaycontroller 156, respectively. For a virtual click wheel, the click wheelmay be either an opaque or semitransparent object that appears anddisappears on the touch screen display in response to user interactionwith the device. In some embodiments, a virtual click wheel is displayedon the touch screen of a portable multifunction device and operated byuser contact with the touch screen.

The device 100 also includes a power system 162 for powering the variouscomponents. The power system 162 may include a power management system,one or more power sources (e.g., battery, alternating current (AC)), arecharging system, a power failure detection circuit, a power converteror inverter, a power status indicator (e.g., a light-emitting diode(LED)) and any other components associated with the generation,management and distribution of power in portable devices.

The device 100 may also include one or more optical sensors 164. FIGS.1A and 1B show an optical sensor coupled to an optical sensor controller158 in I/O subsystem 106. The optical sensor 164 may includecharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. The optical sensor 164 receives light from theenvironment, projected through one or more lens, and converts the lightto data representing an image. In conjunction with an imaging module 143(also called a camera module), the optical sensor 164 may capture stillimages or video. In some embodiments, an optical sensor is located onthe back of the device 100, opposite the touch screen display 112 on thefront of the device, so that the touch screen display may be used as aviewfinder for either still and/or video image acquisition. In someembodiments, an optical sensor is located on the front of the device sothat the user's image may be obtained for videoconferencing while theuser views the other video conference participants on the touch screendisplay. In some embodiments, the position of the optical sensor 164 canbe changed by the user (e.g., by rotating the lens and the sensor in thedevice housing) so that a single optical sensor 164 may be used alongwith the touch screen display for both video conferencing and stilland/or video image acquisition.

The device 100 may also include one or more proximity sensors 166. FIGS.1A and 1B show a proximity sensor 166 coupled to the peripheralsinterface 118. Alternately, the proximity sensor 166 may be coupled toan input controller 160 in the I/O subsystem 106. The proximity sensor166 may perform as described in U.S. patent application Ser. No.11/241,839, “Proximity Detector In Handheld Device,” filed Sep. 30,3005; Ser. No. 11/240,788, “Proximity Detector In Handheld Device,”filed Sep. 30, 3005; Ser. No. 11/620,702, “Using Ambient Light Sensor ToAugment Proximity Sensor Output”; Ser. No. 11/586,862, “AutomatedResponse To And Sensing Of User Activity In Portable Devices,” filedOct. 24, 2006; and Ser. No. 11/638,251, “Methods And Systems ForAutomatic Configuration Of Peripherals,” which are hereby incorporatedby reference in their entirety. In some embodiments, the proximitysensor turns off and disables the touch screen 112 when themultifunction device is placed near the user's ear (e.g., when the useris making a phone call). In some embodiments, the proximity sensor keepsthe screen off when the device is in the user's pocket, purse, or otherdark area to prevent unnecessary battery drainage when the device is alocked state.

The device 100 may also include one or more accelerometers 168. FIGS. 1Aand 1B show an accelerometer 168 coupled to the peripherals interface118. Alternately, the accelerometer 168 may be coupled to an inputcontroller 160 in the I/O subsystem 106. The accelerometer 168 mayperform as described in U.S. Patent Publication No. 20050190059,“Acceleration-based Theft Detection System for Portable ElectronicDevices,” and U.S. Patent Publication No. 20060017692, “Methods AndApparatuses For Operating A Portable Device Based On An Accelerometer,”both of which are which are incorporated herein by reference in theirentirety. In some embodiments, information is displayed on the touchscreen display in a portrait view or a landscape view based on ananalysis of data received from the one or more accelerometers. Forexample, in response to detecting the portable multifunction device inan orientation that comprises a vertical or substantially verticalorientation (e.g., within a predetermined number of degrees (such as 20,30, 40 or 45 degrees) of being vertical) of the long axis of the touchscreen display, the device may display an application interface in aportrait view (e.g., UI 7000P, FIG. 7P). Conversely, in response todetecting the portable multifunction device in an orientation thatcomprises a vertical or substantially vertical orientation (e.g., withina predetermined number of degrees (such as 20, 30, 40 or 45 degrees) ofbeing vertical) of the short axis of the touch screen display, thedevice may display an application interface in a landscape view.

In some embodiments, the software components stored in memory 102 mayinclude an operating system 126, a communication module (or set ofinstructions) 128, a contact/motion module (or set of instructions) 130,a graphics module (or set of instructions) 132, a text input module (orset of instructions) 134, a Global Positioning System (GPS) module (orset of instructions) 135, and applications (or set of instructions) 136.

The operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

The communication module 128 facilitates communication with otherdevices over one or more external ports 124 and also includes varioussoftware components for handling data received by the RF circuitry 108and/or the external port 124. The external port 124 (e.g., UniversalSerial Bus (USB), FIREWIRE, etc.) is adapted for coupling directly toother devices or indirectly over a network (e.g., the Internet, wirelessLAN, etc.). In some embodiments, the external port is a multi-pin (e.g.,30-pin) connector that is the same as, or similar to and/or compatiblewith the 30-pin connector used on iPod (trademark of Apple Computer,Inc.) devices.

The contact/motion module 130 may detect contact with the touch screen112 (in conjunction with the display controller 156) and other touchsensitive devices (e.g., a touchpad or physical click wheel). Thecontact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred, determining if there is movement ofthe contact and tracking the movement across the touch screen 112, anddetermining if the contact has been broken (i.e., if the contact hasceased). Determining movement of the point of contact may includedetermining speed (magnitude), velocity (magnitude and direction),and/or an acceleration (a change in magnitude and/or direction) of thepoint of contact. These operations may be applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments, thecontact/motion module 130 and the display controller 156 also detectscontact on a detects contact on a click wheel.

The graphics module 132 includes various known software components forrendering and displaying graphics on the touch screen 112, includingcomponents for changing the intensity of graphics that are displayed. Asused herein, the term “graphics” includes any object that can bedisplayed to a user, including without limitation text, web pages, icons(such as user-interface objects including soft keys), digital images,videos, animations and the like.

The text input module 134, which may be a component of graphics module132, provides soft keyboards for entering text in various applications(e.g., contacts 137, email 140, IM 141, blogging 142, browser 147, andany other application that needs text input).

The GPS module 135 determines the location of the device and providesthis information for use in various applications (e.g., to telephone 138for use in location-based dialing, to camera 143 and/or blogger 142 aspicture/video metadata, and to applications that provide location-basedservices such as weather widgets, local yellow page widgets, andmap/navigation widgets).

The applications 136 may include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   a contacts module 137 (sometimes called an address book or        contact list);    -   a telephone module 138;    -   a video conferencing module 139;    -   an e-mail client module 140;    -   an instant messaging (IM) module 141;    -   a blogging module 142;    -   camera module 143 for still and/or video images;    -   an image management module 144;    -   a video player module 145;    -   a browser module 147;    -   calendar module 148;    -   widget modules 149, which may include weather widget 149-1,        stocks widget 149-2, calculator widget 149-3, alarm clock widget        149-4, dictionary widget 149-5, and other widgets obtained by        the user, as well as user-created widgets 149-6;    -   widget creator module 150 for making user-created widgets 149-6;    -   search module 151;    -   video and music player module 152, which merges video player        module 145 and music player module 146;    -   notes module 153;    -   map module 154; and/or    -   online video module 155.

Examples of other applications 136 that may be stored in memory 102include other word processing applications, JAVA-enabled applications,encryption, digital rights management, voice recognition, and voicereplication.

In conjunction with touch screen 112, display controller 156, contactmodule 130, graphics module 132, and text input module 134, the contactsmodule 137 may be used to manage an address book or contact list,including: adding name(s) to the address book; deleting name(s) from theaddress book; associating telephone number(s), e-mail address(es),physical address(es) or other information with a name; associating animage with a name; categorizing and sorting names; providing telephonenumbers or e-mail addresses to initiate and/or facilitate communicationsby telephone 138, video conference 139, e-mail 140, or IM 141; and soforth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact module130, graphics module 132, and text input module 134, the telephonemodule 138 may be used to enter a sequence of characters correspondingto a telephone number, access one or more telephone respective telephonenumber, conduct a conversation and disconnect or hang up when theconversation is completed. As noted above, the wireless communicationmay use any of a plurality of communications standards, protocols andtechnologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact module 130, graphics module132, text input module 134, contact list 137, and telephone module 138,the videoconferencing module 139 may be used to initiate, conduct, andterminate a video conference between a user and one or more otherparticipants.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, the e-mail client module 140 may be used to create, send,receive, and manage e-mail. In conjunction with image management module144, the e-mail module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, the instant messaging module 141 may be used to enter asequence of characters corresponding to an instant message, to modifypreviously entered characters, to transmit a respective instant message(for example, using a Short Message Service (SMS) or Multimedia MessageService (MMS) protocol for telephony-based instant messages or usingXMPP, SIMPLE, or IMPS for Internet-based instant messages), to receiveinstant messages and to view received instant messages. In someembodiments, transmitted and/or received instant messages may includegraphics, photos, audio files, video files and/or other attachments asare supported in a MMS and/or an Enhanced Messaging Service (EMS). Asused herein, “instant messaging” refers to both telephony-based messages(e.g., messages sent using SMS or MMS) and Internet-based messages(e.g., messages sent using XMPP, SIMPLE, or IMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact module 130, graphics module 132, text inputmodule 134, image management module 144, and browsing module 147, theblogging module 142 may be used to send text, still images, video,and/or other graphics to a blog (e.g., the user's blog).

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact module 130,graphics module 132, and image management module 144, the camera module143 may be used to capture still images or video (including a videostream) and store them into memory 102, modify characteristics of astill image or video, or delete a still image or video from memory 102.

In conjunction with touch screen 112, display controller 156, contactmodule 130, graphics module 132, text input module 134, and cameramodule 143, the image management module 144 may be used to arrange,modify or otherwise manipulate, label, delete, present (e.g., in adigital slide show or album), and store still and/or video images.

In conjunction with touch screen 112, display controller 156, contactmodule 130, graphics module 132, audio circuitry 110, and speaker 111,the video player module 145 may be used to display, present or otherwiseplay back videos (e.g., on the touch screen or on an external, connecteddisplay via external port 124).

In conjunction with touch screen 112, display system controller 156,contact module 130, graphics module 132, audio circuitry 110, speaker111, RF circuitry 108, and browser module 147, the music player module146 allows the user to download and play back recorded music and othersound files stored in one or more file formats, such as MP3 or AACfiles. In some embodiments, the device 100 may include the functionalityof an MP3 player, such as an iPod (trademark of Apple Computer, Inc.).

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, and text inputmodule 134, the browser module 147 may be used to browse the Internet,including searching, linking to, receiving, and displaying web pages orportions thereof, as well as attachments and other files linked to webpages.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, e-mail module 140, and browser module 147, the calendarmodule 148 may be used to create, display, modify, and store calendarsand data associated with calendars (e.g., calendar entries, to do lists,etc.).

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, and browser module 147, the widget modules 149 aremini-applications that may be downloaded and used by a user (e.g.,weather widget 149-1, stocks widget 149-2, calculator widget 149-3,alarm clock widget 149-4, and dictionary widget 149-5) or created by theuser (e.g., user-created widget 149-6). In some embodiments, a widgetincludes an HTML (Hypertext Markup Language) file, a CSS (CascadingStyle Sheets) file, and a JavaScript file. In some embodiments, a widgetincludes an XML (Extensible Markup Language) file and a JavaScript file(e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, and browser module 147, the widget creator module 150 may beused by a user to create widgets (e.g., turning a user-specified portionof a web page into a widget).

In conjunction with touch screen 112, display system controller 156,contact module 130, graphics module 132, and text input module 134, thesearch module 151 may be used to search for text, music, sound, image,video, and/or other files in memory 102 that match one or more searchcriteria (e.g., one or more user-specified search terms).

In conjunction with touch screen 112, display controller 156, contactmodule 130, graphics module 132, and text input module 134, the notesmodule 153 may be used to create and manage notes, to do lists, and thelike.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, GPS module 135, and browser module 147, the map module 154may be used to receive, display, modify, and store maps and dataassociated with maps (e.g., driving directions; data on stores and otherpoints of interest at or near a particular location; and otherlocation-based data).

In conjunction with touch screen 112, display system controller 156,contact module 130, graphics module 132, audio circuitry 110, speaker111, RF circuitry 108, text input module 134, e-mail client module 140,and browser module 147, the online video module 155 allows the user toaccess, browse, receive (e.g., by streaming and/or download), play back(e.g., on the touch screen or on an external, connected display viaexternal port 124), send an e-mail with a link to a particular onlinevideo, and otherwise manage online videos in one or more file formats,such as H.264. In some embodiments, instant messaging module 141, ratherthan e-mail client module 140, is used to send a link to a particularonline video. Embodiments of user interfaces and associated processesusing online video module 155 are described further below.

Each of the above identified modules and applications correspond to aset of instructions for performing one or more functions describedabove. These modules (i.e., sets of instructions) need not beimplemented as separate software programs, procedures or modules, andthus various subsets of these modules may be combined or otherwiserearranged in various embodiments. For example, video player module 145may be combined with music player module 146 into a single module (e.g.,video and music player module 152, FIG. 1B). In some embodiments, memory102 may store a subset of the modules and data structures identifiedabove. Furthermore, memory 102 may store additional modules and datastructures not described above.

In some embodiments, the device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen 112 and/or a touchpad. By using a touch screenand/or a touchpad as the primary input/control device for operation ofthe device 100, the number of physical input/control devices (such aspush buttons, dials, and the like) on the device 100 may be reduced.

The predefined set of functions that may be performed exclusivelythrough a touch screen and/or a touchpad include navigation between userinterfaces. In some embodiments, the touchpad, when touched by the user,navigates the device 100 to a main, home, or root menu from any userinterface that may be displayed on the device 100. In such embodiments,the touchpad may be referred to as a “menu button.” In some otherembodiments, the menu button may be a physical push button or otherphysical input/control device instead of a touchpad.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screen maydisplay one or more graphics within user interface (UI) 200. In thisembodiment, as well as others described below, a user may select one ormore of the graphics by making contact or touching the graphics, forexample, with one or more fingers 202 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the contact may include a gesture, such as one or moretaps, one or more swipes (from left to right, right to left, upwardand/or downward) and/or a rolling of a finger (from right to left, leftto right, upward and/or downward) that has made contact with the device100. In some embodiments, inadvertent contact with a graphic may notselect the graphic. For example, a swipe gesture that sweeps over anapplication icon may not select the corresponding application when thegesture corresponding to selection is a tap.

The device 100 may also include one or more physical buttons, such as“home” or menu button 204. As described previously, the menu button 204may be used to navigate to any application 136 in a set of applicationsthat may be executed on the device 100. Alternatively, in someembodiments, the menu button is implemented as a soft key in a GUI intouch screen 112.

In one embodiment, the device 100 includes a touch screen 112, a menubutton 204, a push button 206 for powering the device on/off and lockingthe device, volume adjustment button(s) 208, a Subscriber IdentityModule (SIM) card slot 210, a head set jack 212, and a docking/chargingexternal port 124. The push button 206 may be used to turn the poweron/off on the device by depressing the button and holding the button inthe depressed state for a predefined time interval; to lock the deviceby depressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, the device 100 also mayaccept verbal input for activation or deactivation of some functionsthrough the microphone 113.

Attention is now directed towards embodiments of user interfaces (“UI”)and associated processes that may be implemented on a portablemultifunction device 100.

FIG. 3 illustrates an exemplary user interface for unlocking a portableelectronic device in accordance with some embodiments. In someembodiments, user interface 300 includes the following elements, or asubset or superset thereof:

-   -   Unlock image 302 that is moved with a finger gesture to unlock        the device;    -   Arrow 304 that provides a visual cue to the unlock gesture;    -   Time 308;    -   Day 310;    -   Date 312; and    -   Wallpaper image 314.

In some embodiments, the device detects contact with the touch-sensitivedisplay (e.g., a user's finger making contact on or near the unlockimage 302) while the device is in a user-interface lock state. Thedevice moves the unlock image 302 in accordance with the contact. Thedevice transitions to a user-interface unlock state if the detectedcontact corresponds to a predefined gesture, such as moving the unlockimage across channel 306. Conversely, the device maintains theuser-interface lock state if the detected contact does not correspond tothe predefined gesture. As noted above, processes that use gestures onthe touch screen to unlock the device are described in U.S. patentapplication Ser. No. 11/322,549, “Unlocking A Device By PerformingGestures On An Unlock Image,” filed Dec. 23, 2005, and Ser. No.11/322,550, “Indication Of Progress Towards Satisfaction Of A User InputCondition,” filed Dec. 23, 2005, which are hereby incorporated byreference in their entirety. In addition, as described below withrespect to FIG. 7G, an unlock icon (e.g., image 302, arrow 304, and“slide to unlock” channel 306) may be changed to a view-invitation icon(e.g., image 302, arrow 304, and “slide to view” channel 307) when thedevice receives a calendar invitation while the device is locked.

FIGS. 4A and 4B illustrate exemplary user interfaces for a menu ofapplications on a portable multifunction device in accordance with someembodiments. In some embodiments, user interface 400A includes thefollowing elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:    -   Phone 138, which may include an indicator 414 of the number of        missed calls or voicemail messages;    -   E-mail client 140, which may include an indicator 410 of the        number of unread e-mails;    -   Browser 147; and Music player 146; and    -   Icons for other applications, such as:    -   IM 141;    -   Image management 144;    -   Camera 143;    -   Video player 145;    -   Weather 149-1;    -   Stocks 149-2;    -   Blog 142;    -   Calendar 148;    -   Calculator 149-3;    -   Alarm clock 149-4;    -   Dictionary 149-5; and    -   User-created widget 149-6.

In some embodiments, user interface 400B includes the followingelements, or a subset or superset thereof:

-   -   402, 404, 406, 141, 148, 144, 143, 149-3, 149-2, 149-1, 149-4,        410, 414, 138, 140, and 147, as described above;    -   Map 154;    -   Notes 153;    -   Settings 412, which provides access to settings for the device        100 and its various applications 136, as described further        below;    -   Video and music player module 152, also referred to as iPod        (trademark of Apple Computer, Inc.) module 152; and    -   Online video module 155, also referred to as YouTube (trademark        of Google, Inc.) module 155.

In some embodiments, UI 400A or 400B displays all of the availableapplications 136 on one screen so that there is no need to scrollthrough a list of applications (e.g., via a scroll bar). In someembodiments, as the number of applications increase, the iconscorresponding to the applications may decrease in size so that allapplications may be displayed on a single screen without scrolling. Insome embodiments, having all applications on one screen and a menubutton enables a user to access any desired application with at most twoinputs, such as activating the menu button 204 and then activating thedesired application (e.g., by a tap or other finger gesture on the iconcorresponding to the application).

In some embodiments, UI 400A or 400B provides integrated access to bothwidget-based applications and non-widget-based applications. In someembodiments, all of the widgets, whether user-created or not, aredisplayed in UI 400A or 400B. In other embodiments, activating the iconfor user-created widget 149-6 may lead to another UI that contains theuser-created widgets or icons corresponding to the user-created widgets.

In some embodiments, a user may rearrange the icons in UI 400A or 400B,e.g., using processes described in U.S. patent application Ser. No.11/459,602, “Portable Electronic Device With Interface ReconfigurationMode,” filed Jul. 24, 2006, which is hereby incorporated by reference inits entirety. For example, a user may move application icons in and outof tray 408 using finger gestures.

In some embodiments, UI 400A or 400B includes a gauge (not shown) thatdisplays an updated account usage metric for an account associated withusage of the device (e.g., a cellular phone account), as described inU.S. patent application Ser. No. 11/322,552, “Account InformationDisplay For Portable Communication Device,” filed Dec. 23, 2005, whichis hereby incorporated by reference in its entirety.

Figures SA-SM illustrate exemplary user interfaces for displaying andmanaging calendar entries. FIG. 5A illustrates UI 4900A, which displaysa calendar in a list-view mode. UI 4900A includes the following elementsor a subset or superset thereof:

-   -   402, 404, and 406, as described above;    -   today icon 4902;    -   display mode icon 4904;    -   add calendar entry icon 4906;    -   day headers 4908; and    -   calendar entries 4910.

The highlighted portion 4912 of the display mode icon 4904 indicateswhich view of the calendar is being displayed. As shown in FIG. 5A, alist view of the calendar is being displayed, and therefore, thehighlighted portion 4912 corresponds to the list view. In someembodiments, a respective calendar may be displayed in a list, day, ormultiweek view. The multiweek view may include a monthly view. Theappropriate section of the display mode icon 4904 is highlightedaccording to which view of the calendar is being displayed. The term“highlight” is used here to mean displaying in a visually distinctivemanner, such as changing one or more of the following: background color,background fill pattern, bolding, underlining, font color, font, etc.

A user may perform a finger contact within the display mode icon 4904on, or within the area immediately surrounding the desired calendar viewto display.

UI 4900A also includes a today icon 4902, which when activated, forexample by a finger contact, initiates display of today's events in thethen active calendar view (e.g., in the list, day, or month view). Whena user selects the today icon 4902, the corresponding calendar for thecurrent day is displayed.

UI 4900A also includes an add calendar entry icon 4906. The add calendarentry icon 4906 allows a user to add calendar entries to a desired day.As will be described later, FIGS. 5I-5M illustrate exemplary userinterfaces for adding a calendar entry.

In some embodiments, UI 4900A includes a list calendar, which includesday headers 4908 and calendar entries 4910. The day header 4908 appearsabove the corresponding calendar entry or entries for a particular day.In some embodiments, days without any calendar entries are not displayedon the user interface.

A user may scroll through the calendar by making a vertical finger swipe4914 anywhere on the list calendar.

FIG. 5B illustrates UI 4900B, which displays a calendar in a day-viewmode. UI 4900A includes the following elements or a subset or supersetthereof:

-   -   402, 404, 406, 4902, 4904, and 4906 as described above;    -   day forward icon 4922 that when activated (e.g., by a finger tap        of the icon) displays the day-view of the calendar for the        following day;    -   day backward icon 4924 that when activated (e.g., by a finger        tap of the icon) displays the day-view of the calendar for the        preceding day; and    -   time slots 4926.

FIG. 5C illustrates UI 4900C, which displays a calendar in a month-viewmode. UI 4900A includes the following elements or a subset or supersetthereof:

-   -   402, 404, 406, 4902, 4904, and 4906 as described above;    -   month forward icon 4930 that when activated (e.g. by a finger        tap of the icon) displays the month-view of the calendar for the        following month;    -   month backward icon 4932 that when activated (e.g. by a finger        tap of the icon) displays the month-view of the calendar for the        preceding month;    -   monthly calendar 4934 that includes calendar day icon 4936;    -   list of events 4938; and    -   vertical bar 4940, which indicates the portion of the list 4938        being displayed.

UI 4900C a calendar in month-view mode is displayed while simultaneouslydisplaying a list of events 4938 for a selected day. In someembodiments, a respective selected day is indicated by highlighting(e.g., day icon 4936 is highlighted in FIG. 5C).

At a portable multifunction device with a touch screen display, amultiweek calendar is displayed on the touch screen display. A contacton an individual day in the multiweek calendar is detected, and inresponse to detecting the contact on the individual day, at least aportion of a list of events on the contacted individual day is displayedwhile continuing to display the multiweek calendar (FIG. 5C).

In some embodiments, the contact is a finger contact on or near thetouch screen display. In some other embodiments, the contact is a styluscontact on or near the touch screen display.

In some embodiments, the multiweek calendar is a monthly calendar, asillustrated in FIGS. 5C-5H.

As will be described in FIGS. 5D-5G, a user may change the list ofevents 4938 being displayed by making a finger contact on the touchscreen 112 within the grid of the monthly calendar 4934. As shown inFIG. 5D, a user starts with the user's finger touching the highlightedcalendar day icon, as indicated by finger contact area 4950. As seen inFIG. 5D, the list of events 4938 corresponds to the highlighted calendarday icon 4936. The user continues with finger contact 4950 and moves, orscrubs, the user's finger along the touch screen 112 within the grid ofthe monthly calendar 4934 in the direction of the arrow, as demonstratedin FIG. 5D. As the user's finger contact 4950 stops on a particular day,the list of events 4938 being displayed changes accordingly, as shown inFIG. 5E.

In some embodiments, the list of events 4938 is scrollable. In someembodiments, the list of events is configured to scroll in response to afinger gesture on the list of events. In some embodiments, the fingergesture is a swipe gesture.

A gesture on the list of events is detected, and in response todetecting the gesture on the list, list of events scrolls whilecontinuing to display the multiweek calendar. In some embodiments, thegesture is a gesture with a finger.

In some embodiments, contacts with a plurality of days in the multiweekcalendar is sequentially detected, and in response to detecting contactswith the plurality of days, lists of events are sequentially displayedfor at least some of the plurality of days while continuing to displaythe multiweek calendar. In some embodiments, the sequentially detectedcontacts correspond to movement of a single, unbroken finger contactwith the touch screen display, also known as scrubbing, as describedabove.

In some embodiments, in response to detecting contacts with theplurality of days, the plurality of days in the multiweek calendar issequentially highlighted.

In some embodiments, when a user's finger contact continues to scrubalong the touch screen 112 (see FIG. 5F) to a calendar day icon 4936with no corresponding calendar entries, and the finger contact movementstops on such day, no list of events is shown, as illustrated in FIG.5G.

In some embodiments, indicia for each day in the multiweek calendar thathas at least one event is displayed. In some embodiments, the calendarday icon 4936 may indicate whether or not the corresponding day containscalendar entries. In some embodiments, calendar days containingcorresponding calendar entries are indicated with an underscore belowthe date in the calendar day icon 4936, as shown in FIGS. 5C-5H.

FIG. 5H illustrates UI 4900D, which displays a calendar in a month-viewmode according to some embodiments. UI 4900D includes many of the samefeatures as US 4900C, and also includes month scroll bar 4960. Themonthly calendar being displayed corresponds to the highlighted month inthe month scroll bar. When a user performs a vertical finger swipe onthe month scroll bar 4960, this allows the highlighted portion 4962 ofthe month scroll bar 4960 to vertically scroll through the months in themonth scroll bar 4960. Accordingly, the corresponding monthly calendaris also displayed depending on which month in the month scroll bar ishighlighted.

FIGS. 5I-5M illustrate exemplary user interfaces for adding calendarentries. In some embodiments, when a user selects the add calendar icon4906, as shown in FIGS. 5A-5H, the UI 4900E is displayed (FIG. 51). Whena user makes a contact, for example on contact point 4970, and thecontact point requires time entry, the UI 4900F (FIG. 5J) is displayed.UI 4900F includes wheels of time 4974. Vertical finger swipes (asrepresented by vertical doubled headed arrows in FIG. 5J) may beperformed along each vertical column (e.g., a date, hour, minute, orAM/PM column) thereby causing the entries to rotate accordingly. Oncethe desired time entry is reached, enter icon 4976 may be selected andthe appropriate time entry is displayed in the appropriate field in UI49001 (FIG. 5M). In some embodiments, once the desired time entry isreached, the appropriate time entry is displayed in the appropriatefield in UI 4900I (FIG. 5M) without needing to select an enter icon.

In some embodiments, if a user desires to enter an all day event, UI4900G is displayed (FIG. 5K). Finger swipes are performed within thewheel and the date rotates accordingly.

In some embodiments, if repeat icon 4972 in FIG. 5I is selected, UI4900H is displayed (FIG. 5L). A user may have the entry entered for thesame time every week by selected at contact point 4980. Alternately, theuser may have the entry entered for the same time at another interval(e.g., every day, every two weeks, every month, every year, or a customrepeat interval) as indicated by a different user selection within therepeat event UI 4900H. When the event icon 4982 (FIG. 5L) is selected,the appropriate repeat information is displayed in UI 4900I (FIG. 5M).

FIG. 6A illustrates is a flow diagram of a process 600 for displayingand managing calendar entries in accordance with some embodiments. Insome embodiments, the process 600 is performed by a portable electronicdevice with a touch screen display. The device displays a multiweekcalendar on the touch screen display (602), e.g., UI 4900C of FIG. 5C.If a user touches a desired day on the multiweek display, the devicedetects the finger contact on that individual day in the multiweekcalendar (604). As a response to the finger contact on the individualday, the device displays at least a portion of a list of events 4938 onthe contacted individual day while continuing to display the multiweekcalendar (606).

In some embodiments, if a user sequentially contacts the touch screendisplay on a plurality of days, the device sequentially detects thecontact with the plurality of days in the multiweek calendar (608). Inresponse to detecting the contacts, the device sequentially displayslists of events for at least some of the plurality of days whilecontinuing to display the multiweek calendar (610), e.g., FIGS. 5D-5G.

FIG. 6B illustrates is a flow diagram of a process 620 for displayingand managing calendar entries in accordance with some embodiments. Insome embodiments, the process 620 is performed by a portable electronicdevice with a touch screen display. The device displays a multiweekcalendar on the touch screen display (622), e.g., UI 4900C of FIG. 5C.If a user touches a desired day on the multiweek display, the devicedetects the finger contact on the individual day, the device displays atleast a portion of a list of events 4938 on the contacted individual daywhile continuing to display the multiweek calendar (626). If a fingergesture is detected on the list of events being displayed (628), thedevice scrolls through the list of events while continuing to displaythe multiweek calendar (630).

FIGS. 7A-7S illustrate exemplary user interfaces for accessing acalendar application on a portable multifunction device 100 inaccordance with some embodiments. An overview of these user interfacesis provided below.

FIG. 7A shows a device held in a portrait orientation, displaying amultiweek month view (e.g., for October, 2007). The figure showsdetecting a contact 7001 on an individual day 7010 (e.g., Oct. 29, 2007)and displaying at least a portion of a list of events on the contactedindividual day while continuing to display the multiweek calendar. Thelist of events on the contacted individual day 7010 (e.g., Oct. 29,2007) includes an invitation to the event (the agenda review). Inresponse to detecting a contact 7001 (e.g. a finger gesture or a stylus)on a given day on the calendar, the device displays events listed on thecorresponding day, including invitations to events. The list of eventson any given day is scrollable, in response to detecting a gesture onthe list of events. The gesture may be a finger gesture, such as a swipegesture 7003. In some embodiments, a contact 7002 is detected on aninvitation inbox icon 7040, which initiates display of an invitationinbox (e.g., as shown in FIG. 7C).

FIG. 7B shows a device held in a portrait orientation (with asubstantially vertical orientation of a long axis of the touch screen)displaying a list view of daily events for a multiplicity of days. Thelist is vertically scrollable to permit a user to see events on earlieror later days. A set of icons are provided to initiate display of“Today” events, and to initiate display of events in a list view, dayview or month view, in response to detecting a user gesture on thecorresponding icon. An icon 7040 is provided for accessing an invitationinbox and for displaying of a number of unread calendar invitations. Insome embodiments, a contact gesture 7004 is detected on the invitationinbox icon 7040, which initiates display of an invitation inbox (e.g.,as shown on FIG. 7C).

FIG. 7C shows a device held in a portrait orientation, displaying anexemplary list (inbox) of calendar invitations received by the device.In this list, there are two exemplary calendar invitations, first adesign review invitation 7062-1, and second a patent meeting invitation7062-2. In the present example, both invitations are marked as unread,as indicated by the dot 7070 to the left side of each calendarinvitation. In response to detecting a user gesture on the “Done” button7008 in the title bar, the device exits from the calendar invitationinbox. In FIG. 7C, in response to detecting a user selection gesture7007 on the design review invitation 7062-1, the device displays detailsof the invitation, as shown in FIG. 7D.

FIG. 7D shows a device displaying information details of an exemplaryinvitation, the design review invitation 7062-1. These details includethe title of the meeting, location (Diplomacy room), date, time, senderof the invitation (Christie), attendees, and notes regarding themeeting. The calendar invitation also includes a “Show in calendar” icon7082 which if activated by the user (e.g., by finger gesture 7009)initiates display of the invitation in the user's calendar (e.g., asshown in FIG. 7E). The calendar invitation also includes icons for theuser to accept (7091) the meeting, to indicate that the user may attend(7093), and to decline (7095) the meeting. In some embodiments, theaccept icon 7091 is green, the maybe icon 7093 is orange, and thedecline 7095 icon is red.

FIG. 7E shows an exemplary day view (e.g., for Oct. 29, 2007) with anexemplary calendar invitation shown as a tentative calendar event 7092-1(e.g., the design review meeting in Diplomacy room from 1 pm to 3 pm).This exemplary calendar invitation corresponds to the design reviewinvitation discussed in FIGS. 7C-7D. The day view of FIG. 7E isvertically scrollable 7099 to permit a user to see events earlier andlater in the day. In FIG. 7E, the tentative calendar event 7092-1 forthe design review meeting is in conflict with a scheduled event, i.e.,the interview meeting 7094-1 from 2 pm to 4 pm. In response to detectinga gesture 7011 on the invitation inbox icon 7040, the device 100initiates display of the invitation inbox (e.g., UI 7000F, FIG. 7F).

FIG. 7F shows an exemplary list of calendar invitations received by thedevice. In this list, as described above, there are two calendarinvitations 7062, first a design review invitation, and second a patentmeeting invitation. In FIG. 7F, the design review invitation is markedas read (there is no dot 7070-1 for this invitation) and the word‘Accepted’ is displayed, which indicates that the user has accepted thisinvitation. The patent meeting calendar invitation is marked as unread,as indicated by the dot 7070-2. The number of outstanding invitationshas decreased from two in FIG. 7C to one in FIG. 7F, as the designreview meeting has been read and accepted (FIG. 7D).

FIG. 7G shows an exemplary locked device displaying details of acalendar invitation from a party to a user of the device. An exemplaryunlock icon 309 that includes image 302, arrow 304, and “slide tounlock” channel 306 (FIG. 3) has been replaced by an exemplaryview-invitation icon 309 that includes image 302, arrow 304, and “slideto view” channel 307. If the device detects a user request to view thecalendar invitation (e.g., a swipe gesture on image 302 in “slide toview” channel 307), the device immediately displays the calendarinvitation in a calendar application, for example, as shown in FIG. 7D.In some embodiments, detecting a view-invitation gesture causes thedevice to display the invitation inbox (FIG. 7C) instead of theinvitation (FIG. 7D). If no user activation of the view-invitation iconis detected within a predetermined period of time, the device ceases todisplay the portion of the calendar invitation on the touch screendisplay, and changes the view-invitation icon back to the unlock icon.

FIG. 7H shows a calendar invitation alert 7130 displayed over a currentapplication while the device is unlocked. The calendar invitation alertis displayed in response to receipt by the device of a calendarinvitation from a party to a user of the device. The calendar invitationalert displays at least a portion of the calendar invitation on thetouch screen display. The alert includes icons to close (7132) the alertor to view (7134) the calendar invitation. In response to detecting afinger gesture 7014 on “View” icon 7134, the device displays theinvitation in a calendar application (e.g., FIG. 7D). In someembodiments, in response to detecting a finger gesture 7014 on “View”icon 7134, the device displays the invitation inbox (FIG. 7C).

FIG. 7I shows an exemplary calendar invitation icon 7150 in an emailsent by a party (e.g., Greg) to the user of the device. In someembodiments, the calendar invitation icon shows the time of the meeting(1 pm Monday), and the title of the meeting (Design Review). In responseto detecting a finger gesture 7015 on calendar invitation icon 7150, thedevice displays the corresponding invitation in a calendar application(e.g., FIG. 7D). In some embodiments, in response to detecting a fingergesture 7015 on calendar invitation icon 7150, the device displays theinvitation inbox (FIG. 7C). In some embodiments, an area 7160 containsinformation as to when the inbox was last updated and a refresh button3560 to initiate refreshing the email inbox.

FIG. 7J shows a device 100 in a portrait orientation, displaying amultiweek calendar view for a month time period with a scrollable list4938 of calendar events for a particular day (e.g., Oct. 29, 2007). Themulti week calendar view is flat (appears as a flat page) and thescrollable list shows events from different types of calendars (e.g., ahome calendar, a work calendar, and a personal calendar), as indicatedby the three different calendar indicia symbols 7019 next to the events.In some embodiments, the multiweek view also includes a view optionsicon 7180. In some embodiments, in response to detecting a user gesture7018 on the view options icon 7180, the device displays a curled upversion of the calendar interface (e.g., FIG. 7M). In some embodiments,in response to detecting a user gesture 7028 on a Calendars icon 7016,the device displays a calendar options menu, as shown in FIG. 7L.

FIG. 7K shows a device 100 in a portrait orientation displaying a listview of a multiday calendar having a plurality of event types. In someembodiments, each event type is coded (e.g., color or pattern coded withcalendar indicia symbols 7019) for ease of recognition. In someembodiments, in response to detecting a finger gesture (e.g., swipegesture 4914), the device scrolls the list of events on the multidaycalendar. In response to detecting a finger gesture on an event (e.g.,gesture 7020 on the design review event), the device initiates displayof corresponding details for the event. In some embodiments, in responseto detecting a user gesture 7022 on the view options icon 7180, thedevice displays a curled up version of the calendar interface (e.g.,FIG. 7M). In some embodiments, in response to detecting a user gestureon a Calendars icon 7016, the device displays a calendar options menu,as shown in FIG. 7L.

FIG. 7L shows a device 100 displaying a calendar options menu. In someembodiments, in response to detecting a selection gesture on a calendaroption, events from the selected calendar are displayed. In someembodiments, in response to detecting selection gestures on two or moreof the calendar options, events from the selected calendars aredisplayed. In some embodiments, in response to detecting a selectiongesture (e.g., a finger tap gesture 7023) on the “All” calendars option,events from all of the with calendar indicia symbols 7019 so that a userwill recognize the calendar from which each event comes.

FIG. 7M shows a device 100 displaying a curled up page of a multiweekcalendar view, with a view options menu also shown. In some embodiments,the curled up page is shown in response to detecting a user gesture onthe view options icon 7180 (e.g., in FIG. 7J or FIG. 7K). In the curledup version of the calendar interface, an image 7350 of a bent, folded,or otherwise curled page is displayed, which obscures a first part ofthe flat version of the calendar application interface. A roll-up region7353 is displayed over an area formerly occupied by a second portion ofthe flat version of the calendar application interface. The roll-upregion 7353 includes calendar option icons (e.g., 7210, 7220-1, 7220-2,and 7220-3). In response to detecting user selection gestures on one ormore of the calendar option icons a flat version of the calendarapplication interface is displayed with events corresponding to the oneor more calendar option icons upon which user selection gestures weredetected. For example, if a user selects “work,” then calendar eventsfrom the work calendar will be displayed on the flat version of thecalendar interface. In some embodiments, if a user selects “work” and“home,” then calendar events from the work and home calendars will bedisplayed on the flat version of the calendar interface. In someembodiments, a portion of the curled version is displayed in a mannerdistinct from how that portion is displayed in the flat version. In someembodiments, the curled page is displayed as a translucentrepresentation of a portion of the flat version of the calendarinterface. In the curled-up page view, in response to detecting userselection of the view options icon 7180, a flat view is re-displayed,for example, the flat view of FIG. 7J.

FIG. 7N shows a device 100 displaying a single day calendar having aplurality of event types, including an invitation shown as a tentativecalendar event 7092-2. In FIG. 7N, there is an invitation from 1 pm to 3pm for a design review from the work calendar. There is a doctor'sappointment 7094-2 from 4 pm to 6 pm from the home calendar. The singleday calendar of FIG. 7N is scrollable in response to a gesture 7026. Aset of icons 4902, 4904 are provided to initiate display of “Today”events, and to initiate display of events in a list view, day view ormonth view, in response to detecting a user gesture on the correspondingicon. An icon 7040 is provided for accessing an invitation inbox and fordisplaying a number of unread calendar invitations. In FIG. 7N, inresponse to detecting a user gesture 7025 on the “Month” view, thedevice initiates display of the month view (e.g., FIG. 70).

FIG. 70 shows a device 100 displaying a multiweek calendar 4934 alongwith a list 4938 of events for a selected day (e.g., Oct. 25, 2007). Thelist of events includes events from a plurality of calendars. FIG. 70displays two events on the day of Oct. 25, 2007. These events are codedto indicate the calendar from which the event came. One of the events isa calendar invitation from the work calendar, namely the design reviewat 1 pm. The other event is a calendar appointment from the homecalendar, namely the doctor's appointment at 4 pm. The event list isscrollable in response to a user gesture. The event list changes inresponse to a user contact on an individual day in the multiweekcalendar, while continuing to display the multiweek calendar. In someembodiments, the list of events on the contacted individual day includesan invitation to an event (e.g. tentative calendar event 7092-2, FIG.70).

FIG. 7P shows a device held in a portrait orientation displaying acalendar view for a first time period (e.g., a day). In someembodiments, the portrait orientation corresponds to a substantiallyvertical orientation of the long axis of the touch screen. The day viewis scrollable in response to a user gesture 7027, permitting a user tosee a plurality of events in a day. In response to detecting the devicein a landscape orientation, the device changes to a landscape calendarview of a second time period (e.g., a week, FIG. 7Q).

FIG. 7Q shows a device held in a landscape orientation displaying amultiday calendar view for a time period longer than the day view of theportrait orientation of FIG. 7P. In some embodiments, the landscapeorientation corresponds to a substantially vertical orientation of theshort axis of the touch screen. In some embodiments, the multiday viewis a week view. In some embodiments, the week view is scrollable inresponse to a user gesture, permitting a user to easily view all of thehours in a week. In some embodiments, if the device in a portraitorientation shows a week view, then in response to detecting rotation ofthe device to a landscape orientation, the device displays a multiweekview, such as a month view. In some embodiments, if the device in aportrait orientation shows a multiweek view, then in response torotating the device to a landscape orientation, the device displays aview of a plurality of months.

FIG. 7R shows a device 100 held in a portrait orientation displaying amultiweek calendar view for a month time period. In some embodiments,the portrait orientation corresponds to a substantially verticalorientation of the long axis of the touch screen. In response todetecting the device in a landscape orientation, the device changes to alandscape calendar view of a second time period (e.g., FIG. 7S, acalendar that displays multiple months that include the multiple weeksin FIG. 7R).

FIG. 7S shows a device held in a landscape orientation displaying amulti-month calendar view for a time period longer than the multi-weekview of the portrait orientation of FIG. 7R. In some embodiments, thelandscape orientation corresponds to a substantially verticalorientation of the short axis of the touch screen. In some embodiments,the multi-month view is a three-month view. In some embodiments, themulti-month view is scrollable in response to a user gesture, permittinga user to see months earlier and later than a currently displayed view.In some embodiments, if the device in a portrait orientation shows amulti-week view (e.g., FIG. 7R), then in response to detecting rotationof the device to a landscape orientation, the device displays amulti-month view, such as a three month view (e.g., FIG. 7S). In someembodiments, if the device in a portrait orientation shows a multiweekview, then in response to rotating (7510, 7520) the device to alandscape orientation, the device displays a view of a plurality ofmonths.

The user interfaces in FIGS. 7A-7S are used to illustrate the processesdescribed below with respect to FIGS. 8A-8F. Additional details on theseuser interfaces are provided below.

In some embodiments, UI 7000A (FIG. 7A) includes the following elements,or a subset or superset thereof:

-   -   402, 404, 406, 4912, 4930, 4932, 4934, 4938, 4902, 4904, and        4940, as described above; and    -   an invitation inbox selector 7040, that when activated (e.g. by        a finger tap 7002) initiates display of an invitation inbox        interface (e.g., UI 7000C, FIG. 7C).

In some embodiments, the inbox selector 7040 displays the number ofunread calendar invitations in the inbox (e.g., “2” in FIG. 7A).

In some embodiments, UI 7000B (FIG. 7B) includes the following elements,or a subset or superset thereof:

-   -   402, 404, 406, 4902, 4904, 4908, 4912, and 7040, as described        above; and    -   a scrollable (e.g., in response to a swipe gesture 7005)        calendar list view 7050 that displays a list of events 4910 and        the time period (e.g., day 4908) with which the events are        associated.

In some embodiments, UI 7000C (FIG. 7C) includes the following elements,or a subset or superset thereof:

-   -   402, 404, and 406, as described above;    -   a calendar invitation inbox 7060 that displays a list of        calendar invitations 7062 and, in some embodiments, details        (e.g., day, time, location) for the calendar invitations;    -   Calendar invitation(s) 7062 or portion(s) thereof;    -   Done icon 7008 that when activated (e.g., by a finger gesture)        initiates exiting the calendar invitation inbox; and    -   Unread calendar invitation indicia 7070 that indicate that the        corresponding calendar invitation has not been read.

In some embodiments, calendar invitation inbox 7060 includes a title barthat displays the number of unread invitations (e.g., Invites(2)). Insome embodiments, in response to detecting a gesture on the list ofcalendar invitations (e.g., finger swipe gesture 7006 on invitation7062-I), the device scrolls the list. In some embodiments, in responseto detecting a gesture on a calendar invitation (e.g., finger tapgesture 7007 on invitation 7062-1), the device initiates display of aninterface (e.g., UI 7000D, FIG. 7D) that provides details of theselected calendar invitation.

In some embodiments, UI 7000D (FIG. 7D) includes the following elements,or a subset or superset thereof:

-   -   402, 404, 406, and 7062, as described above;    -   a “show in calendar” icon 7082 that when activated (e.g., by        figure gesture 7009) initiates display of the invitation in a        calendar (e.g., as shown in FIG. 7E);    -   a “return to calendar invitation inbox” icon 7084 that when        activated (e.g., by finger gesture) initiates display of the        calendar invitation inbox (e.g., FIG. 7C);    -   a “previous invitation” icon 7086 that when activated (e.g., by        finger gesture) initiates display of the previous calendar        invitation in the calendar invitation inbox;    -   a “next invitation” icon 7088 that when activated (e.g., by        finger gesture) initiates display of the next calendar        invitation in the calendar invitation inbox;    -   an “accept invitation” icon 7091 that when activated (e.g., by        finger gesture) initiates acceptance of calendar invitation        (e.g., 7062-1);    -   a “maybe” icon 7093 that when activated (e.g., by finger        gesture) initiates tentative acceptance of calendar invitation        (e.g., 7062-1); and    -   a “decline invitation” icon 7095 that when activated (e.g., by        finger gesture) initiates rejection of calendar invitation        (e.g., 7062-1).

In some embodiments, UI 7000E (FIG. 7E) includes the following elements,or a subset or superset thereof:

-   -   402, 404, 406, 4902, 4904,4910, 4912, and 7040, as described        above;    -   a calendar day view 7090; and    -   a calendar invitation (e.g., 7062-1 from UI 7000C, FIG. 7C)        shown as a tentative calendar event 7092-1, where a dotted        border, the word “Invitation,” or other visual indicator shows        the tentative nature of event 7092; and    -   tentative calendar event (e.g., event 7094-1 overlaps with event        7092-1 between 2-3 pm).

In some embodiments, UI 7000F (FIG. 7F) includes the following elements,or a subset or superset thereof:

-   -   402, 404, 406, 7008, 7060, 7062, and 7070, as described above.

In this example, a user has accepted the first meeting 7062-1. As aresult the first meeting 7062-1 is marked as accepted, and the unreadindicator 7070 for the first meeting is no longer present. The number ofunread invitations indicated in the top bar has been reduced from two toone.

In some embodiments, UI 7000G (FIG. 7G) includes the following elements,or a subset or superset thereof:

-   -   302, 304, 307, 308, 310, 312, and 314, as described above;    -   an alert 7120 indicating a new calendar invitation has been        received, which may be displayed over a wallpaper image 314        while the device 100 is in a locked mode; and    -   view-invitation icon 309 that when activated (e.g., by a finger        gesture on image 302) initiates display of an interface (e.g.,        UI 7000D, FIG. 7D) giving details of the calendar invitation.

In some embodiments, detecting a view-invitation gesture causes thedevice to display the invitation inbox (FIG. 7C) instead of theinvitation (FIG. 7D).

In some embodiments, UI 7000H (FIG. 7H) includes the following elements,or a subset or superset thereof:

-   -   308, 310, and 312, as described above;    -   an alert 7130 indicating a new calendar invitation has been        received, displayed over a current application while the device        100 is in an unlocked mode; and    -   a close icon 7132 that when activated (e.g., by a finger        gesture) ceases display of the alert 7130; and    -   a view icon 7134 that when activated (e.g., by a finger gesture        7014) initiates display of an interface (e.g., UI 7000D, FIG.        7D) giving details of the calendar invitation.

In some embodiments, detecting a gesture 7014 on view icon 7134 causesthe device to display the invitation inbox (FIG. 7C) instead of theinvitation (FIG. 7D).

In some embodiments, UI 7000I (FIG. 7I) includes the following elements,or a subset or superset thereof:

-   -   402, 404, 406, 7084, 7086, and 7088, as described above;    -   an email 7140;    -   a calendar invitation icon 7150 that when activated (e.g., by a        finger gesture 7015) initiates display of a invitation in a        calendar application (e.g., FIG. 7D); and    -   a refresh icon 3560 that when activated (e.g., by a finger        gesture) initiates a refresh of the inbox.

In some embodiments, UI 7000J (FIG. 7J) includes the following elements,or a subset or superset thereof:

-   -   402, 404, 406, 4902, 4904, 4906, 4912, 4930, 4932, 4934, and        7040, as described above;    -   a view options icon 7180 that when activated (e.g., by a finger        gesture 7018) initiates display of a calendar options menu with        a curled up version of the calendar interface (e.g., FIG. 7M) or        other calendar options menu (e.g., FIG. 7L);    -   a calendar options icon 7016 that when activated (e.g., by a        finger gesture 7028) initiates display of a calendar options        menu with a curled up version of the calendar interface (e.g.,        FIG. 7M) or other calendar options menu (e.g., FIG. 7L); and    -   calendar indicia symbols 7019 that indicate which calendar an        event comes from (e.g., an event from a work calendar includes        symbol 7019-1, an event from a home calendar includes symbol        7019-2, and an event from a personal calendar includes symbol        7019-3).

In some embodiments, UI 7000J (FIG. 7J) includes view options icon 7180(activated by a finger gesture 7018) or calendar options icon 7016, butnot both.

In some embodiments, UI 7000K (FIG. 7K) includes the following elements,or a subset or superset thereof:

-   -   402, 404, 406, 4902, 4904, 4908, 4910, 4912, 7040, 7050, 7016,        7180, as described above.

In some embodiments, UI 7000L (FIG. 7L) includes the following elements,or a subset or superset thereof:

-   -   402, 404, and 406, as described above;    -   a calendar option menu 7205;    -   an all calendar option icon 7210 that when activated (e.g., by a        finger gesture 7023) initiates display of a calendar (e.g., FIG.        7J or FIG. 7K) that shows events from all of the individual        calendars; and    -   individual calendar option icons 7220 that when activated (e.g.,        by a finger gesture) initiates display of a calendar that shows        events from the corresponding individual calendar;

In some embodiments, UI 7000M (FIG. 7M) includes the following elements,or a subset or superset thereof:

-   -   402, 404, 406, 4906, 4930, 4932, 3560, 7016, and 7180, as        described above;    -   a portion 7351 of a flat version of a calendar application        interface;    -   an image 7350 of a bent, folded, or otherwise curled page that        obscures a portion of the flat version of the calendar        application interface; and    -   a roll-up region 7353 in a display region formerly occupied by a        another portion of the flat version of the calendar application        interface, wherein the roll-up region includes a plurality of        calendar option icons (e.g., 7210, 7220-1, 7220-2, and 7220-3).

In some embodiments, UI 7000N (FIG. 7N) includes the following elements,or a subset or superset thereof:

-   -   402, 404, 406, 4902, 4904, 4912, 7040, 7090, 7092, 7094 as        described above.

In some embodiments, UI 7000O (FIG. 7O) includes the following elements,or a subset or superset thereof:

-   -   402, 404, 406, 4902, 4904, 4912 4930, 4932, 4934, 4938, 4940,        7040, 7092, and 7094, as described above.

In some embodiments, UI 7000P (FIG. 7P) includes the following elements,or a subset or superset thereof:

-   -   402, 404, 406, 4902, 4904, 4906, 4912, 4930, 4932, and 7090, as        described above.

In some embodiments, UI 7000Q (FIG. 7Q) includes the following elements,or a subset or superset thereof:

-   -   402, 404, 406, 4902, 4904, 4906, and 4912 as described above;        and    -   a calendar in landscape orientation displaying a scrollable        multiday view 7600, for a time period longer than and including        the day view of the portrait orientation of FIG. 7P.

In some embodiments, in response to detecting rotation of the device(e.g., 7530 and 7540) from a landscape orientation to a portraitorientation, the device displays a single-day calendar in a portraitorientation, such as that of UI 7000P, FIG. 7P.

In some embodiments, UI 7000R (FIG. 7R) includes the following elements,or a subset or superset thereof:

-   -   402, 404, 406, 4902, 4904, 4906, 4912, 4930, 4932, 4934, 4938,        and 4940, as described above.

In some embodiments, in response to detecting rotation of the device(e.g., 7510 and 7520) from a portrait orientation to a landscapeorientation, the device displays a multi-month calendar in a landscapeorientation, such as that of UI 7000S, FIG. 7S.

In some embodiments, UI 7000S (FIG. 7S) includes the following elements,or a subset or superset thereof:

-   -   402, 404, 406, 4902, 4904, 4906, 4912, 4930, and 4932, as        described above; and    -   a calendar in landscape orientation displaying a scrollable        multi-month view 7650, for a time period longer than and        including the multi-week view of the portrait orientation of        FIG. 7R.

In some embodiments, in response to detecting rotation of the device(e.g., 7530 and 7540) from a landscape orientation to a portraitorientation, and in response to the rotation, the device displays amultiweek calendar for a duration less than the multi-month calendar ina portrait orientation, such as that of UI 7000R, FIG. 7R.

The user interfaces in FIGS. 7A-7S are used to illustrate the processesdescribed below with respect to Figure(s) 8A-8F.

FIG. 8A is flow diagram illustrating a method 800 of operating acalendar application in accordance with some embodiments. The method 800is performed on a portable electronic device with a touch screen display(e.g., portable multifunction device 100). The method 800 provides asimple and intuitive way for a user to switch between a first calendartime period and a second longer time period. This is a convenient way tochange the time period viewed without having to access menus or engagein other combinations of actions.

The portable electronic device executes (801) a calendar application.When the device is held in a portrait orientation, the device displays(802) a calendar in a first view, showing events for a first time periodin the first view (e.g., UI 7000P, FIG. 7P). The device detects (804) achange in orientation of the device to a landscape orientation, and inresponse, displays the calendar in a second view, showing events for asecond time period that is longer than and includes the first timeperiod (e.g., UI 7000Q, FIG. 7Q).

In some embodiments, when the device is held in a portrait orientation,the device displays (806) a calendar in a day view, showing events for asingle day in the day view (e.g., UI 7000P, FIG. 7P). The device detects(808) a change in orientation of the device to a landscape orientation,and in response, displays the calendar in a multiday view, showingevents for a multiplicity of days, the multiplicity of days includingthe single day (e.g., UI 7000Q, FIG. 7Q)

In some embodiments, when the device is held in a portrait orientation,the device displays (810) a calendar in a week view, showing events fora single week in the week view. The device detects (812) a change inorientation of the device to a landscape orientation, and in response,displays the calendar in a multiweek view, showing events for amultiplicity of weeks, the multiplicity of weeks including the singleweek. In some embodiments, the multiweek view is a month view (814).

FIG. 8B is flow diagram illustrating a method 820 of operating acalendar application in accordance with some embodiments. The method 820is performed at a portable multifunction device with a touch screendisplay (e.g., portable multifunction device 100). The touch screenincludes a long axis, a short axis, a landscape view and a portraitview. The method 820 provides a simple and intuitive way for a user toswitch between a first time period and a second longer time period. Thisis a convenient way to change the time period viewed without having toaccess menus or engage in other combinations of actions.

The portable multifunction device executes (822) a calendar application.The device detects (824) the portable multifunction device in a firstorientation that comprises a vertical or substantially verticalorientation of the long axis. In response to detecting the portablemultifunction device in the first orientation that comprises thevertical or substantially vertical orientation of the long axis, thedevice displays (826) a calendar for a first time period in the portraitview (e.g., UI 7000P, FIG. 7P). The device detects (828) the portablemultifunction device in a second orientation that comprises a verticalor substantially vertical orientation of the short axis. In response todetecting the portable multifunction device in the second orientationthat comprises the vertical or substantially vertical orientation of theshort axis, the device displays (830) a calendar for a second timeperiod in the landscape view. The second time period is longer than andincludes the first time period (e.g., UI 7000Q, FIG. 7Q).

In some embodiments, the calendar for the first time period shows eventsfor the first time period and the calendar for the second time periodshows events for the second time period (832). In some embodiments, thefirst time period is a day (e.g., UI 7000P, FIG. 7P) and the second timeperiod is a plurality of days (e.g., 3-7 days, with 7 days shown in UI7000Q, FIG. 7Q) (834). In some embodiments, the first time period is aday (e.g., UI 7000P, FIG. 7P) and the second time period is a week(e.g., UI 7000Q, FIG. 7Q) (836). In some embodiments, the first timeperiod is a week and the second time period is a plurality of weeks(e.g., 3-5 weeks) (838). In some embodiments, the first time period is aweek and the second time period is a month (840). In some embodiments,the first time period is a month (e.g., UI 7000R, FIG. 7R) and thesecond time period is a plurality of months (e.g., 3 months, as shown inUI 7000S, FIG. 7S) (842).

FIG. 8C is flow diagram illustrating a method 850 of operating acalendar application in accordance with some embodiments. The method 850is performed at a portable multifunction device with a touch screendisplay (e.g., portable multifunction device 100). The method 850provides a simple and intuitive way for a user to view events forindividual days in a multiweek calendar while simultaneously viewing themultiweek calendar.

The device displays (852) a multiweek calendar on the touch screendisplay (e.g., UI 7000J, FIG. 7J). In some embodiments, the multiweekcalendar is a monthly calendar (854).

The device detects (856) a contact (e.g., 7017) on an individual day inthe multiweek calendar. In some embodiments, the contact is a fingercontact (858). In some embodiments, the contact is a stylus contact(860).

In response to detecting the contact on the individual day, the devicedisplays (862) at least a portion of a list of events (e.g., 4938) onthe contacted individual day while continuing to display the multiweekcalendar (e.g., 4934). The list of events on the contacted individualday includes an invitation to an event (e.g., tentative calendar event7092-2, “Design Review (Invitation),” FIG. 7J).

In some embodiments, the list of events is scrollable (864). In someembodiments, the list of events is configured to scroll in response to afinger gesture on the list of events (866). In some embodiments thefinger gesture is a swipe gesture (868).

In some embodiments, the device detects (870) a gesture 4938 on the listof events. In response to detecting the gesture on the list (e.g.,7029), the device scrolls (874) the list of events while continuing todisplay the multiweek calendar. In some embodiments, the gesture is aswipe gesture with a finger (872).

FIG. 8D is flow diagram illustrating a method 880 of displaying andselecting calendar options in accordance with some embodiments. Themethod 880 is performed at a computing device with a touch screendisplay (e.g., portable multifunction device 100). The method 880provides a simple and intuitive way for a user to select calendaroptions.

A computing device with a touch screen display displays (882) a flatversion (e.g., UI 7000J, FIG. 7J) of a calendar application interface onthe touch screen display. In response to detecting a user gesture (e.g.,7018, FIG. 7J) on a view options icon (e.g., 7180) while the flatversion of the calendar application interface is displayed, the devicedisplays (884) a curled version (e.g., UI 7000M, FIG. 7M) of thecalendar application interface. The curled version of the calendarapplication interface includes an image of a bent, folded, or otherwisecurled page (e.g., 7350) that obscures a first portion of the flatversion of the calendar application interface, and a roll-up region(e.g., 7353) in a display region formerly occupied by a second portionof the flat version of the calendar application interface. The roll-upregion includes a plurality of calendar option icons (e.g., 7210, 7220),each respective calendar option icon in the plurality of calendar optionicons responsive to a user selection gesture on the respective calendaroption icon. The device detects (886) a user selection gesture on one ormore of the plurality of calendar option icons. The device redisplays(888) the flat version of the calendar application interface withinformation corresponding to the one or more calendar option icons uponwhich user selection gestures were detected.

In some embodiments, the device detects (890) user selection gestures onat least two of the plurality of calendar option icons. The deviceredisplays (892) the flat version of the calendar application interfacewith information corresponding to the at least two of the plurality ofoption icons upon which user selection gestures were detected.

In some embodiments, the curled version of the calendar applicationinterface includes (894) a third portion (e.g., 7351, FIG. 7M) of theflat version of the calendar application interface. In some embodiments,the third portion is displayed (896) in the curled version of thecalendar application interface in a manner that is visually distinctfrom display of the third portion in the flat version of the calendarapplication interface.

In some embodiments, the flat version of the calendar applicationinterface is redisplayed (8102) in response to detecting a second usergesture on the view options icon.

In some embodiments, the device displays (8104) a roll up animation thattransitions from displaying the flat version of the calendar applicationinterface to displaying the curled version of the calendar applicationinterface. In some embodiments, the device displays (8106) a roll downanimation that transitions from displaying the curled version of thecalendar application interface to redisplaying the flat version of thecalendar application interface with information corresponding to the oneor more calendar option icons upon which user selection gestures weredetected.

In some embodiments, the curled page includes (8108) an inverted,translucent representation of a portion of the flat version of thecalendar application interface. In some embodiments, the curled pageincludes (8110) a translucent representation of a portion of the flatversion of the calendar application interface.

In some embodiments, the user selection gestures are finger gestures onthe touch screen display (8112).

FIG. 8F is flow diagram illustrating a method 8120 of receivingdisplaying calendar invitations in accordance with some embodiments. Themethod 8120 is performed on a portable multifunction device with a touchscreen display (e.g., portable multifunction device 100). The method8120 provides a simple and intuitive way for a user to view a calendarinvitation if the device receiving the invitation is locked.

The device receives (8122) a calendar invitation, from a party to a userof the device, while the device is locked (e.g., UI 7000G, FIG. 7G). Thedevice displays (8124) at least a portion of the calendar invitation(e.g., 7120) on the touch screen display while the device remainslocked. In response to detecting a user request to view the calendarinvitation, the device immediately displays (8126) the calendarinvitation in a calendar application.

In some embodiments, while the device is locked, the device changes(8128) an unlock icon (e.g., 306, FIG. 7C) to a view-invitation icon(e.g., 309, FIG. 7G) when displaying the portion 7120 of the calendarinvitation.

In some embodiments, if no user selection of the view-invitation icon isdetected within a predetermined period of time (e.g., 5 or 10 seconds),the device ceases (8130) to display the portion of the calendarinvitation on the touch screen display, and changes (8132) theview-invitation icon back to the unlock icon.

FIG. 9 is a schematic diagram of a communications system 900 thatprovides infrastructure support for a portable multifunction device 100in accordance with some embodiments. FIG. 9 shows a portablemultifunction device 100 communicating (for example, synchronizing,sending data, receiving data, and sending or receiving voice or videocalls) over a wireless network 910 (for example, WiFi or a cellphonenetwork) to a wired network 920 (for example, the Internet). The device100 accesses at least one server 930 to send and receive email, calendarschedule updates, and other voice or data information. In someembodiments, the at least one server 930 is provided by a serviceprovider. In some embodiments, the at least one server is provided by acorporate network.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the invention and its practical applications, to therebyenable others skilled in the art to best utilize the invention andvarious embodiments with various modifications as are suited to theparticular use contemplated.

What is claimed:
 1. A non-transitory computer readable storage mediumstoring one or more programs configured to be executed by one or moreprocessors of an electronic device with a display, the one or moreprograms including instructions for: displaying, on the display, a monthview of a calendar application without displaying a list view of userevents, the month view including a month of a year displayed in acontent region of the calendar application and the month view includingall weeks of the month; receiving a user input to display a split viewof the calendar application; in response to receiving the user input todisplay the split view of the calendar application, displaying the monthview in a first portion of the content region and display the list viewof user events in a second portion of the content region, wherein thelist view of user events displayed in the second portion are organizedinto a continuous series of rows, each row associated with acorresponding user event from the list view of user events; receiving auser input in the first portion to display another month; in response toreceiving the user input in the first portion, displaying another monthof the year in the first portion; receiving a user input in the secondportion to browse user events; and in response to receiving the userinput in the second portion, displaying at least one additional userevent in the list view of user events displayed in the second portion.2. The non-transitory computer readable storage medium of claim 1,wherein a size of each row of the continuous series of rows is uniformregardless of a duration of each event.
 3. The non-transitory computerreadable storage medium of claim 1, wherein the calendar applicationfurther includes a control region comprising a today affordance.
 4. Thenon-transitory computer readable storage medium of claim 3, whereinreceiving the user input to display the split view further comprises:receiving a user selection of the today affordance.
 5. Thenon-transitory computer readable storage medium of claim 1, whereindisplaying the month view in the first portion and displaying the listview of user events in the second portion further comprises: determininga size of the first portion based on a total number of weeks of themonth to display in the first portion; and dividing the content regioninto the first portion and the second portion based on the determinedsize of the first portion.
 6. The non-transitory computer readablestorage medium of claim 1, wherein displaying the list view of userevents in the second portion further comprises: receiving a user inputto cease displaying the split view of the calendar application; and inresponse to receiving the user input to cease displaying the split viewof the calendar application: displaying the month view in the contentregion, and ceasing displaying the list view of user events in thecontent region.
 7. The non-transitory computer readable storage mediumof claim 1, wherein each row associated with a corresponding user eventincludes a first portion and a second portion, the first portioncomprising at least a description of the corresponding user event andthe second portion comprising a start time and an end time of thecorresponding user event.
 8. The non-transitory computer readablestorage medium of claim 1, wherein displaying the list view of userevents in the second portion comprises: automatically displaying thelist view of user events of a current day in the second portion of thecontent region responsive to receiving the user input.
 9. Thenon-transitory computer readable storage medium of claim 1, whereindisplaying the month view in the first portion of the content regioncomprises: highlighting a current day in the first portion.
 10. Thenon-transitory computer readable storage medium of claim 1, wherein theone or more programs further include instructions for: receiving a userselection of a day from the month view displayed in the first portion;and in response to receiving the user selection of the day from themonth view displayed in the first portion: automatically displaying, inthe second portion, a list view of user events of the selected day; andhighlighting the selected day in the first portion.
 11. Thenon-transitory computer readable storage medium of claim 1, wherein theuser input in the first portion to display another month includes a tapgesture or a swipe gesture in the first portion.
 12. The non-transitorycomputer readable storage medium of claim 3, and wherein the one or moreprograms further include instructions for: receiving a user selection ofthe today affordance; and in response to receiving user selection of thetoday affordance: displaying a current month of the year in the firstportion with a current day highlighted; and displaying the list view ofuser events for the current day in the content region.
 13. An electronicdevice comprising: a display; one or more processors; and memory storingone or more programs configured to be executed by the one or moreprocessors, the one or more programs including instructions for:displaying, on the display, a month view of a calendar applicationwithout displaying a list view of user events, the month view includinga month of a year displayed in a content region of the calendarapplication and the month view including all weeks of the month;receiving a user input to display a split view of the calendarapplication; in response to receiving the user input to display thesplit view of the calendar application, displaying the month view in afirst portion of the content region and display the list view of userevents in a second portion of the content region, wherein the list viewof user events displayed in the second portion are organized into acontinuous series of rows, each row associated with a corresponding userevent from the list view of user events; receiving a user input in thefirst portion to display another month; in response to receiving theuser input in the first portion, displaying another month of the year inthe first portion; receiving a user input in the second portion tobrowse user events; and in response to receiving the user input in thesecond portion, displaying at least one additional user event in thelist view of user events displayed in the second portion.
 14. Theelectronic device of claim 13, wherein a size of each row of thecontinuous series of rows is uniform regardless of a duration of eachevent.
 15. The electronic device of claim 13, wherein the calendarapplication further includes a control region comprising a todayaffordance.
 16. The electronic device of claim 15, wherein receiving theuser input to display the split view further comprises: receiving a userselection of the today affordance.
 17. The electronic device of claim13, wherein displaying the month view in the first portion anddisplaying the list view of user events in the second portion furthercomprises: determining a size of the first portion based on a totalnumber of weeks of the month to display in the first portion; anddividing the content region into the first portion and the secondportion based on the determined size of the first portion.
 18. Theelectronic device of claim 13, wherein displaying the list view of userevents in the second portion further comprises: receiving a user inputto cease displaying the split view of the calendar application; and inresponse to receiving the user input to cease displaying the split viewof the calendar application: displaying the month view in the contentregion, and ceasing displaying the list view of user events in thecontent region.
 19. The electronic device of claim 13, wherein each rowassociated with a corresponding user event includes a first portion anda second portion, the first portion comprising at least a description ofthe corresponding user event and the second portion comprising a starttime and an end time of the corresponding user event.
 20. The electronicdevice of claim 13, wherein displaying the list view of user events inthe second portion comprises: automatically displaying the list view ofuser events of a current day in the second portion of the content regionresponsive to receiving the user input.
 21. The electronic device ofclaim 13, wherein displaying the month view in the first portion of thecontent region comprises: highlighting a current day in the firstportion.
 22. The electronic device of claim 13, wherein the one or moreprograms further include instructions for: receiving a user selection ofa day from the month view displayed in the first portion; and inresponse to receiving the user selection of the day from the month viewdisplayed in the first portion: automatically displaying, in the secondportion, a list view of user events of the selected day; andhighlighting the selected day in the first portion.
 23. The electronicdevice of claim 13, wherein the user input in the first portion todisplay another month includes a tap gesture or a swipe gesture in thefirst portion.
 24. The electronic device of claim 15, and wherein theone or more programs further include instructions for: receiving a userselection of the today affordance; and in response to receiving userselection of the today affordance: displaying a current month of theyear in the first portion with a current day highlighted; and displayingthe list view of user events for the current day in the content region.25. A method, comprising: at a computing device with a display:displaying, on the display, a month view of a calendar applicationwithout displaying a list view of user events, the month view includinga month of a year displayed in a content region of the calendarapplication and the month view including all weeks of the month;receiving a user input to display a split view of the calendarapplication; in response to receiving the user input to display thesplit view of the calendar application, displaying the month view in afirst portion of the content region and displaying the list view of userevents in a second portion of the content region, wherein the list viewof user events displayed in the second portion are organized into acontinuous series of rows, each row associated with a corresponding userevent from the list view of user events; receiving a user input in thefirst portion to display another month; in response to receiving theuser input in the first portion, displaying another month of the year inthe first portion; receiving a user input in the second portion tobrowse user events; and in response to receiving the user input in thesecond portion, displaying at least one additional user event in thelist view of user events displayed in the second portion.
 26. The methodof claim 25, wherein a size of each row of the continuous series of rowsis uniform regardless of a duration of each event.
 27. The method ofclaim 25, wherein the calendar application further includes a controlregion comprising a today affordance.
 28. The method of claim 27,wherein receiving the user input to display the split view furthercomprises: receiving a user selection of the today affordance.
 29. Themethod of claim 25, wherein displaying the month view in the firstportion and displaying the list view of user events in the secondportion further comprises: determining a size of the first portion basedon a total number of weeks of the month to display in the first portion;and dividing the content region into the first portion and the secondportion based on the determined size of the first portion.
 30. Themethod of claim 25, wherein displaying the list view of user events inthe second portion further comprises: receiving a user input to ceasedisplaying the split view of the calendar application; and in responseto receiving the user input to cease displaying the split view of thecalendar application: displaying the month view in the content region,and ceasing displaying the list view of user events in the contentregion.
 31. The method of claim 25, wherein each row associated with acorresponding user event includes a first portion and a second portion,the first portion comprising at least a description of the correspondinguser event and the second portion comprising a start time and an endtime of the corresponding user event.
 32. The method of claim 25,wherein displaying the list view of user events in the second portioncomprises: automatically displaying the list view of user events of acurrent day in the second portion of the content region responsive toreceiving the user input.
 33. The method of claim 25, wherein displayingthe month view in the first portion of the content region comprises:highlighting a current day in the first portion.
 34. The method of claim25, further including: receiving a user selection of a day from themonth view displayed in the first portion; and in response to receivingthe user selection of the day from the month view displayed in the firstportion: automatically displaying, in the second portion, a list view ofuser events of the selected day; and highlighting the selected day inthe first portion.
 35. The method of claim 25, wherein the user input inthe first portion to display another month includes a tap gesture or aswipe gesture in the first portion.
 36. The method of claim 27, furtherincluding: receiving a user selection of the today affordance; and inresponse to receiving user selection of the today affordance: displayinga current month of the year in the first portion with a current dayhighlighted; and displaying the list view of user events for the currentday in the content region.